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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful governance context — MCP approvals are configurable while business workflow approvals always apply — but it does not say what happens when approval is missing, whether results are paginated, or what the read scope actually covers.

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?

It is short, but the leading 'Use this when working with RetailHardHat budgets records in the connected organization' is filler and the approval sentence reads as boilerplate. The only substantive clause, 'Read committed budget amounts,' is buried in the middle rather than 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?

An output schema exists and annotations are rich, so return values and safety do not need repeating. Still, for a single-parameter read tool the description leaves the identifier's meaning and the relationship to get_budget/list_site_budgets unexplained, which is the main thing an agent needs to call it 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?

There is one required parameter, budgetId, with 0% schema description coverage and no mention anywhere in the description. The description does not explain whether this is a project budget, site budget, or template budget identifier, or how a caller should obtain it — a meaningful gap with only one parameter to document.

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 second sentence, 'Read committed budget amounts,' gives a specific verb (read) and resource (committed budget amounts), which is clearer than the name alone. However, it never distinguishes this from close siblings like get_budget, get_budget_approval, list_site_budgets, or summarize_budget_overruns, so an agent cannot tell which one to pick from the description.

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?

'Use this when working with RetailHardHat budgets records in the connected organization' is a generic context statement that applies equally to dozens of budget-related siblings. There is no when-not guidance, no mention of prerequisites, and no routing to an alternative tool such as get_budget for base budget data.

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