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

Goes well beyond the annotations: it discloses that no change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called, that approval requirements are administrator-configurable, that business workflow approvals always apply, and that approved/locked budgets cannot be modified. For a destructive, non-idempotent mutation this is exactly the context an agent needs.

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?

Front-loads the usage trigger and the draft-only constraint, then the approval mechanics. The final sentence about configurable approval requirements is somewhat verbose but still relevant to how the call will behave.

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?

Purpose, scope restrictions, and the full approval lifecycle are all covered, and an output schema exists so return values need not be described. The remaining gap is field-level parameter guidance, which is a parameter-semantics issue rather than an overall completeness failure.

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 schema has two required params, one of them a nested object with five editable fields (name, notes, unitCount, assumptions, squareFootage) and additionalProperties:false. The description says nothing about budgetId, which fields are updatable, or whether omitted fields are preserved or cleared, so it fails to compensate for the coverage gap.

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?

States a specific verb ('Edit') and resource ('a draft budget'), and scopes it to RetailHardHat budgets in the connected organization. It implicitly distinguishes itself from line-item and template siblings by naming the parent budget record, though it does not name an explicit alternative.

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?

Gives a clear selection condition ('Edit a draft budget; cannot bypass approved/locked restrictions') and explains the required approval path via execute_approved_action. It doesn't explicitly point to sibling tools such as update_budget_line_item for sub-record edits, but the when-to-use context is clear.

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