generate_report

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

Description notes async behavior and that it's a write operation (consistent with readOnlyHint=false). Discloses immediate return and polling need, but does not cover potential failures or rate limits.

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?

Concise and well-structured: purpose line, async pattern, then parameter details. No wasted words, front-loaded with essential information.

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 async behavior, polling, and download URL, but omits explicit response format and error handling. With no output schema, a bit more detail on immediate response would help.

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?

With 0% schema coverage, description fully explains each parameter: definition_id sourced from list_report_definitions, resource_ids required with guidance, target optional. Adds context beyond schema.

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?

Clearly states the tool triggers report generation from a template, with the verb 'trigger generation' and specific resource. Distinguishes from siblings like get_report and list_report_definitions.

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?

Provides explicit async usage pattern: returns immediately, poll get_report until COMPLETED, then use download_url. Explains parameter usage and that resource_ids is required despite schema default.

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