list_budgets

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

Describes output fields (names, IDs, dates) and implies read-only behavior. No annotations exist, so description carries burden; it covers the key behavioral trait of returning budget metadata.

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?

Three efficient sentences: purpose, output summary, usage guidance. No waste, front-loaded with core action.

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?

Simple tool with no parameters and an output schema. Description sufficiently explains what it returns and how to use the result, making it complete for agent understanding.

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?

No parameters, and schema coverage is 100%. Description adds value by listing return fields, which compensates for the lack of parameter information. Baseline for 0 params is 4.

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?

Clearly states it lists all budgets for the authenticated YNAB user. The verb 'list' and resource 'budgets' are specific, and no sibling tool overlaps in purpose.

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 notes that the budget ID from this tool should be used with other tools to target a specific budget, providing clear context for when to use it. Lacks explicit 'when not to use' but is sufficient given sibling diversity.

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