generate_report

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

No annotations provided, so description carries full burden. Discloses non-obvious behaviors: max 7 days, operation can take up to 5 minutes, API has usage limit of 4 reports per user. Does not explicitly state read-only, but report generation implies no mutation.

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?

Description is a single paragraph with four sentences. First sentence states core purpose, then alternative, then caveats. No redundancy, but could be slightly trimmed. For a report tool, length is acceptable.

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?

Given no output schema, description explains return format (individual message with recipient, status, operator, reference). Covers parameter constraints and limitations. Missing error handling details, but sufficient for typical use.

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% (all parameters described). Description adds value by re-emphasizing max 7-day range and explaining 'sandbox' parameter purpose. Not significantly beyond schema, so baseline 3 is appropriate.

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 uses specific verb 'Genera' (generates) and noun 'reporte detallado de mensajes' with scope 'en un rango de fechas (MÁXIMO 7 DÍAS)'. It distinguishes from sibling 'get_report_details' by stating returns individual messages vs. aggregates.

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?

Explicitly states when to use this tool (for detailed individual messages) and when to use alternative 'get_report_details' (for quick aggregates). Provides constraints: max 7 days, API limit of 4 reports per user, and potential 5-minute wait. No explicit 'when not to use' but alternative covers it.

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