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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing that the edit is gated: no change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called, and that org admins can configure MCP approval while business workflow approvals always apply. That is exactly the kind of non-obvious, async-gated mutation behavior an agent must know before calling.

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 approval-gating sentences are dense and valuable, but the leading "Use this when working with RetailHardHat budgets records in the connected organization" is boilerplate that occupies the highest-attention position without earning it. Tightening that clause and front-loading "Edit a budget line item" would improve structure.

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 approval lifecycle is covered and an output schema exists so return values need no explanation. But for a destructive mutation with a 16-field nested payload and no field descriptions anywhere, the description leaves the agent guessing about update semantics and which fields are optional versus required.

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?

Schema description coverage is 0% and the nested `data` object exposes 16 undocumented fields (amount, category enum, quantity, unitCost, contingency fields, assigneeId), yet the description says nothing about them. Critically, it never clarifies whether `data` is a partial patch or a full replacement, which is the single most important semantic for a destructive update.

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 gives a clear verb+resource ("Edit a budget line item"), which is specific enough to act on. However, the opening clause ("Use this when working with RetailHardHat budgets records") is a generic preamble that adds no distinguishing information, and the description never separates this tool from near-identical siblings such as update_budget, update_project_budget_item, or update_change_request_line_item.

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" implies a context but never states when to pick this over update_budget or update_project_budget_item. The approval prerequisites are stated, but they describe the mechanics of the call rather than when the tool is the right choice.

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