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

The annotations already declare this as a read-only, idempotent, non-destructive operation. The description is consistent with those annotations and adds that the tool reads a 'saved report definition' rather than report results, but it does not describe permissions, errors, or other behavioral details.

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 description is a single front-loaded sentence with no wasted text. For a simple getter, the brevity is appropriate.

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?

The output schema and annotations reduce what the description must explain, and the tool has only one parameter. However, the description still lacks parameter guidance and sibling differentiation, leaving notable gaps for an agent selecting among many report-related tools.

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?

The schema has one required parameter, reportId, with pattern and length constraints but 0% description coverage. The description only indirectly implies that reportId identifies a saved report; it does not explain where to obtain the ID or add meaningful semantics beyond the 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?

The description states a specific verb and resource: 'Read a saved report definition.' This is clearer than the title alone, but it does not explicitly distinguish the tool from siblings such as list_reports, preview_report, or export_report.

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?

The description gives no explicit guidance on when to use this tool versus list_reports, preview_report, export_report, or other report-related siblings. Usage is only implied by the need to retrieve a saved report definition by ID.

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