list_account_summary_reports

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states that it lists reports and calls a GET endpoint, implying read-only behavior, but does not mention authentication requirements, pagination behavior, or what the response contains beyond what the output schema might imply.

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 two short sentences with no filler. It front-loads the primary purpose and then gives parameter placement hints. It is concise but could be better structured to separate intent from usage.

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 tool with generic parameters and no annotations, the description is insufficient. It does not explain what constitutes an 'account summary report', how to distinguish this from the account-scoped sibling, or any prerequisite context. An agent would struggle to correctly invoke it without additional domain knowledge.

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 zero specific property definitions (all generic objects with additionalProperties), so the description's guidance on where to place route IDs and query values adds some meaning. However, it is vague—'route IDs' is ambiguous—and does not enumerate valid query parameters or value formats.

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 verb and resource: 'List account summary reports' and identifies the API endpoint. However, it does not explicitly differentiate from the sibling tool 'list_account_summary_reports_for_account', leaving an agent to infer the distinction based on names alone.

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 provides no guidance on when to use this tool versus alternatives. It mentions parameter placement ('Put route IDs in path_params...') but does not explain the appropriate context for selecting this list operation over get_account_summary_report or the account-scoped sibling.

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