reports

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

The verb 'View' implies read-only behavior, and no annotations contradict this. However, no explicit disclosure of side effects or permissions is given, though none seem needed.

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?

A single concise sentence that immediately communicates the tool's purpose and key capabilities. No wasted words.

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 or annotations, the description reasonably covers the tool's inputs and outputs. It could mention the required action parameter or error conditions, but the schema fills the gap.

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 covers all parameters with descriptions. The description enriches meaning by providing business context (KPIs, financial summaries, compliance status) for the action enum values, going beyond the schema's terse descriptions.

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 clearly states the tool is for viewing organizational reports and lists three specific types (dashboard, financial summaries, compliance status), which distinguishes it from sibling tools that manage entities.

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?

No explicit guidance on when to use this tool vs alternatives. Context signals and sibling names imply it's for reporting, but no direct instruction is provided.

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