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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false. The description adds genuine context beyond that: submission routes into a business approval workflow and organizational MCP approval requirements may also be layered on. It does not state what happens on resubmission of an already-submitted budget, which matters given idempotentHint=false.

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, front-loaded with the action, then the non-approval clarification, then the configuration caveat. No filler and no repetition of the title.

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 no explanation, and the mutation semantics are partly covered by annotations. What remains missing is discriminating guidance versus submit_budget_for_approval and any description of the nested data payload, which leaves the definition adequate but under-specified for a submission tool.

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 single parameter is a nested object with notes, entityId and entityType — none of which are mentioned in the description. The agent gets no explanation that entityId is the budget UUID or that notes is free-text context for approvers, so the description fails to compensate for the schema 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?

The description states a specific verb and resource ('Submit an existing budget to the configured business approval flow') and negates a likely misreading ('Does not approve it'). However, it does not differentiate from the near-identical sibling submit_budget_for_approval, which an agent could easily confuse with this tool.

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?

'Does not approve it' implies that approval is a separate action (decide_budget_approval_request), but no alternative is named and no explicit when-to-use condition is given. The presence of a sibling with an almost identical name makes the missing routing guidance a real gap rather than a stylistic one.

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