List Budget Views

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context about pagination ('Returns a paginated JSON array... includes pagination metadata') and the endpoint, which is useful but does not go beyond what the annotations already convey regarding safety.

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 concise (three sentences) and well-structured: first sentence states the core purpose, second gives usage guidance, third details pagination and response metadata. No extraneous information.

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 that this is a simple list tool with no output schema, the description adequately covers what the tool does, what it returns, and how to control pagination. It does not explain all nuances (e.g., sort format), but the schema covers that. It is complete enough for an agent to use correctly.

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 input schema has 100% description coverage, so each parameter is already explained. The description mentions 'page and per_page to control pagination', reinforcing the schema. No additional parameter details are provided, but the schema already suffices.

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 action ('Return a list') and the resource ('all Budget Views for a project'), using a specific verb and resource. It distinguishes from sibling tools that deal with budget line items or modifications by specifying 'Budget Views'.

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 usage context: 'Use this to enumerate Budget records when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly mention when not to use or list alternatives, but the guidance is clear enough for typical scenarios.

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