Ejecutar un informe guardado

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds polling behavior for async reports (pending field) beyond annotations 'readOnlyHint: true' and 'openWorldHint: true'. No contradictions; provides useful behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with primary action, no redundant words. Efficient and focused.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers essential behavior (run by id, return rows, polling, optional overrides). Lacks details on return format or error handling, but adequate for a tool with 3 params and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by stating period/filters are optional overrides, clarifying their role beyond the schema's structural definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it runs a saved report by ID and returns rows, with polling for async reports. It implicitly distinguishes from sibling 'beebole_list_reports' which lists reports, making purpose specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explains optional period/filters to override but does not explicitly state when to use this tool versus alternatives (e.g., when to use a synchronous report vs async, or when to use list_reports first). Usage context is implied not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.