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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds value by disclosing what comes back (status, spend, remaining, per-operation usage), which matters since there is no output schema. It says nothing about behavior for an unknown or expired budgetId, which would be the next useful disclosure.

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?

A single short fragment with zero waste, but it leads with a list of return fields rather than a statement of action. It is concise at the cost of being under-specified rather than efficiently informative.

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 one-parameter read tool with no output schema, describing the returned fields covers much of the missing information. However, the provenance and format of the required budgetId are absent from both schema and description, which is a real gap for actually invoking it.

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?

There is one required parameter (budgetId) with 0% schema description coverage, so the description carries the full burden of explaining it. It says nothing about the format of budgetId or where the agent should obtain one (presumably from request_budget), leaving the single parameter undocumented.

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 enumerates what the tool returns (status, spend, remaining, per-operation usage) but never states a verb or resource explicitly — the retrieval action is only implied by the name and title. It is distinguishable from close_budget and request_budget by the field list, but an agent has to infer 'fetches budget info' rather than read it.

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?

No guidance on when to call this versus siblings such as request_budget (to obtain a budget) or close_budget (to terminate one), and no stated prerequisites. The agent must derive the usage pattern from the tool name alone.

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