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

Annotations already cover read/write and destructive flags, and the description adds valuable behavioral context: the operation may affect multiple items and is subject to configurable MCP approval plus always-applicable business workflow approvals. It still does not explain idempotency or exactly which items are touched.

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 description is short and front-loads the action before the caution and approval notes. The reference to the 'existing screen service' is somewhat opaque, but overall it avoids unnecessary length.

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?

With an output schema present, return values need not be explained here. The description covers review and approval considerations, but for a non-idempotent mutation it remains silent on whether repeated calls duplicate items and on how the approved contracts are selected.

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 only parameter, siteId, is not named or explained in the description. The phrase 'this site's approved contracts' loosely ties to siteId, but it does not compensate for the missing parameter 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: building/adding budget items from a site's approved contracts. It does not, however, distinguish this from nearby siblings such as create_site_budget, create_budget_line_item, or sync_budget_line_item_from_bid.

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?

It implies usage when a site has approved contracts and adds a useful precondition to review them first. It does not explicitly compare when to use this versus related budget-creation or contract-sync tools, nor does it describe exclusions.

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