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

Beyond the annotations, the description explains that this creates a draft only, that current-budget rules still apply, and that no change occurs until a human approves the exact request and execute_approved_action is called. It also discloses that MCP approval requirements are administrator-configurable while business workflow approvals always apply.

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 purpose is front-loaded in the second sentence and the approval constraints are relevant, so the description is usable. The opening RetailHardHat budgets sentence is somewhat boilerplate and the approval details are repeated across several sentences.

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 description covers the critical approval and draft behavior well, and an output schema exists so return values need not be explained. However, for a mutation tool with a nested data object and 0% schema description coverage, the lack of parameter semantics and alternative-tool guidance leaves a meaningful gap.

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 description does not explain siteId, the nested data object, or fields such as name, unitCount, assumptions, and squareFootage. The schema supplies structure and required fields, but the description fails to compensate for the missing semantic documentation.

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 gives a specific verb and resource: "Create a draft site budget." It is clear what the tool creates, but it does not explicitly distinguish this from close siblings such as create_site_budget_from_contracts or set_current_site_budget.

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 phrase "Use this when working with RetailHardHat budgets records" provides only a broad trigger, and the approval-workflow details give context. However, it does not name alternatives, exclusions, or the conditions that would favor a different budget-creation tool.

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