Azure Budget List

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

With no annotations, the description carries the burden of behavioral disclosure. It specifies that the tool returns current spend, thresholds, and alert status, which implies a read-only list operation. However, it does not explicitly state safety, error behavior, pagination, or prerequisites, leaving some gaps for the agent.

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 two concise sentences: the first states purpose and return details, the second adds practical usage context (WAF/CAF). No wasted words, and key information is front-loaded.

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?

The tool is a list operation with a single well-documented parameter and no output schema. The description covers the return content and gives usage scenarios, which is reasonably complete. It does not mention pagination or handling of empty results, but for a list tool of this simplicity, the provided information is largely sufficient.

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 already provides 100% coverage of the 'scope' parameter with examples and CAF guidance, so the description adds no additional parameter semantics beyond what the schema offers. Given the high schema coverage, the baseline of 3 applies.

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 tool 'lists all cost budgets at a given scope' with a specific verb and resource, and includes the return fields (current spend, thresholds, alert status). This distinguishes it from siblings like azure_budget_get (single budget) and azure_budget_create/delete, 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 provides clear usage context with WAF Cost Optimization and CAF scenarios, explicitly stating when this tool should be used for budget coverage verification. It does not explicitly mention alternative tools or exclusions, but the context is sufficiently clear.

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