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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context that the output is semicolon-separated CSV, but it does not add further behavioral details such as download mechanics, authentication needs, 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?

The core purpose and routing guidance are front-loaded and easy to scan. However, the trailing English keyword list includes terms like chart, heatmap, and dashboard that do not add operational value for selecting this CSV export tool.

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?

For a single-parameter, read-only export tool with rich annotations and complete schema coverage, the description provides enough context to select and invoke it correctly. It covers purpose, format, alternatives, and parameter provenance without needing to explain return values in detail.

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% and the only parameter is documented as 'Report-ID'. The description adds meaningful provenance by stating that onto_report_index supplies the report_id, which helps the agent obtain a valid value.

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?

The description states a specific action and output format: export a report as a semicolon-separated CSV download. It also explicitly distinguishes this tool from onto_report_json and onto_report_show, so an agent can choose it without inspecting sibling schemas.

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?

It gives clear use cases (exports and spreadsheet work) and names the correct alternatives for code processing (onto_report_json) and display (onto_report_show). It also tells the agent where to obtain the required report_id (onto_report_index).

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