list_budgets

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns budget names, IDs, and last modified dates, which adds behavioral context beyond the input schema. However, it lacks details on permissions, rate limits, or error handling, which are important for a tool involving user data.

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 a single, efficient sentence that front-loads the purpose ('Get all budgets for the authenticated user') and follows with output details. Every part earns its place without redundancy, making it highly concise and well-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?

Given the tool's low complexity (0 parameters, no output schema), the description is adequate but has gaps. It explains what the tool does and the return values, but without annotations or an output schema, it lacks details on authentication needs, data format, or potential limitations, making it minimally complete.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter semantics, but this is acceptable given the lack of parameters. A baseline of 4 is appropriate as it compensates by not misleading about parameters.

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 specific action ('Get all budgets') and resource ('for the authenticated user'), and distinguishes it from sibling tools like 'get_budget' (singular) by indicating it retrieves multiple budgets. It provides explicit output details (budget names, IDs, and last modified dates), making the purpose unambiguous.

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 implies usage by specifying it retrieves budgets for the authenticated user, suggesting it should be used when listing all budgets rather than a specific one (as with 'get_budget'). However, it does not explicitly state when to use this tool versus alternatives like 'list_accounts' or provide exclusions, leaving some context to inference.

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