get-custom-reports

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

No annotations are provided, so the description must carry the full behavioral burden. 'Retrieve' implies a read-only operation, but the description does not confirm safety, permissions, rate limits, pagination, or whether archived reports are included; it adds little beyond the tool name.

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, front-loaded sentence with no redundant or filler text. It communicates the core action and scope immediately.

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 zero-parameter read tool, the purpose is clear, but with no output schema or annotations the description does not explain the return shape or whether results are paginated or filtered. It is minimally adequate but leaves some ambiguity about what 'every saved custom report' includes.

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 tool takes zero parameters and the schema explicitly states no arguments are accepted. With no parameters to document, the baseline for parameter semantics is 4, and the description appropriately does not invent parameter details.

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?

States a specific verb ('Retrieve') and resource ('every saved custom report'), and scopes it to the budget's Reports section. The resource is distinct from all sibling tools, which cover accounts, transactions, budgets, and other report types, so an agent can select it without opening the schema.

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 only states what the tool returns. It gives no when-to-use guidance, no prerequisites, and no alternatives among the many sibling reporting tools (e.g., get-dashboards, category-trends), leaving the agent to infer that it is for saved custom reports.

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