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

Annotations only declare the basic write/idempotency profile; the description adds genuinely critical behavior not in structured fields: the call is gated by financial approval, no change occurs until a human approves the exact request, and execute_approved_action must then be invoked. That two-phase execution model is exactly the kind of trait 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 core 'Create a project budget item' is buried behind a generic preamble sentence about RetailHardHat budgets records, but the remaining sentences are dense and load-bearing. It is appropriately short with only minor filler at the front.

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, so return values need not be explained, and the approval-gating behavior is thoroughly covered. The remaining hole is parameter meaning for the nested data object, which the description never addresses despite 0% schema coverage.

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's fields are documented only as restated names ('category', 'description', 'notes', 'planned Amount'). The description says nothing about projectId or the shape of data (e.g. whether plannedAmount is a currency string, what category values exist), so it fails to compensate for the coverage gap on a tool with a nested object parameter.

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 states a specific verb and resource ('Create a project budget item'), which is clear enough to act on. It does not, however, distinguish this tool from close siblings like create_budget_line_item, create_project_budget_template_item, or create_site_budget, leaving the agent to infer the distinction from the name alone.

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 the domain but gives no explicit when-to-use versus alternatives, no prerequisites (e.g. budget must exist), and no exclusions. The approval workflow is described but that is a gate, not guidance on choosing this tool over siblings.

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