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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context that approvals are org-configurable and business workflow approvals always apply, which affects call expectations. It does not disclose partial-update semantics (whether omitted fields in `data` are preserved or cleared), which matters greatly for a destructive non-idempotent edit.

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?

Two short sentences with the action front-loaded and no filler. The approval sentence is relevant but slightly tangential to invoking the tool and would be better spent on update semantics.

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?

For a destructive, non-idempotent mutation with a nested required payload and zero schema documentation, the description omits critical information: which fields can be updated, whether the update is a full replace or patch, and what the output schema returns. An output schema exists, so return values need not be described, but the input-side gaps are substantial.

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% across three required params, including a nested `data` object with seven properties, and the description says nothing about any of them. It offers no meaning for `id` vs `itemId`, no explanation of optional vs required update fields, and no clarification of the category/parentCategory relationship.

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 and resource: 'Edit a budget template item,' which an agent can map directly to the mutation. However, it never distinguishes this from the many near-identical siblings such as update_project_budget_template_item, update_purchase_template_item, or update_checklist_template_item, so the agent must infer scope 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?

The second sentence discusses approval configuration but gives no guidance on when to use this tool versus the sibling update_*_template_item tools, nor any prerequisites for editing. It hints that approvals may gate the call but does not tell the agent what to do differently because of that.

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