List Budget View Snapshots

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world. The description adds valuable behavioral details: pagination control with page/per_page, filtering by type, and presence of pagination metadata in response. No contradictions with annotations.

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?

Four sentences with no redundancy. Front-loaded with the core purpose, then usage guidance, then pagination details. Every sentence adds value and is efficiently structured.

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 list tool with 8 params and no output schema, description covers purpose, required parameter, pagination, filtering, and API endpoint. Could optionally detail the response shape beyond 'JSON array', but is sufficient given schema coverage and annotations.

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?

Input schema already describes all 8 parameters with clear descriptions (100% coverage). Description adds context about pagination and filtering by type, but does not elaborate on other filters beyond what schema provides. Baseline 3 is appropriate.

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?

Description clearly states verb 'Returns a list', specifies resource 'project-level snapshots for both project status and ad hoc', and differentiates from related sibling tools like 'list_budget_view_snapshot_detail_rows' and 'list_budget_view_snapshot_summary_rows' by focusing on snapshot listing rather than rows.

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?

Explicitly says when to use: 'Use this to enumerate Budget records when you need a paginated overview, to find IDs, or to filter by query parameters.' This provides clear context, though it does not explicitly mention when not to use or list alternatives, the purpose is well understood.

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