list_agent_budgets

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false). The description adds useful behavioral context: batch operation, all-agents scope, and USD currency. However, it does not disclose return format, pagination, or what happens when agents have no budget, so it doesn't go beyond a 3.

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?

Two short sentences carry the entire definition with no filler. The core purpose and scope are front-loaded, and the 'without N+1' phrase adds practical value without adding bulk.

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 parameterless batch read tool with strong annotations, the description is nearly complete. It states what data is returned (budgets/limits in USD) and for whom (all tenants). The only minor gap is the lack of an explicit response shape or field details, but that is not critical for invoking the tool 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 tool has zero parameters, and the schema already reflects that (100% coverage). With no parameters to describe, the baseline of 4 applies; the description correctly focuses on behavior rather than 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 names a specific action (list), a specific resource (agent budgets in USD), and an explicit scope (all agents in the tenant, in batch). This clearly differentiates it from sibling get_agent_budget, which is singular, even though that sibling is not named directly.

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?

It tells the agent when this tool is valuable: for a consolidated burn-rate view without N+1 calls. It doesn't explicitly say 'use get_agent_budget for a single agent,' but the batch/all semantics and 'without N+1' make the intended use case clear.

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