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

Annotations already carry destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds useful behavioral detail by saying stage_id triggers the target stage's workflow automation as a full stage transition. It does not disclose side effects for fields like is_disqualified or the CV parameter, but the key stage-change behavior is surfaced.

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 only two sentences, with the primary action front-loaded and the important stage_id distinction in the second sentence. Every clause earns its place and there is no filler.

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 five-parameter mutation tool with nested objects, destructiveHint, no output schema, and many related sibling tools, the description is too thin. It does not state what happens when is_disqualified is passed, how it relates to specialized actions like disqualification, or how it compares to other application-moving tools beyond the single stage_id analogy.

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 60%, and the description adds almost no parameter-level meaning beyond stage_id. It repeats the stage_id behavior already present in the schema, but leaves id and is_disqualified semantically undocumented, and adds no guidance on cv or include usage.

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 clearly states the verb/resource ('Update application fields') and adds a meaningful nuance: stage_id performs a full stage transition with automation, likened to hires_move_application. It is more than a tautology and helps distinguish the tool from generic update tools, though it could be more explicit about exactly which application fields are covered.

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?

There is implied guidance: stage_id behavior is said to be like hires_move_application, which informs how the tool may be used. However, there is no explicit statement of when to prefer this tool over related siblings (hires_move_application, hires_disqualify_candidate, hires_reject_application) and no when-not-to-use guidance.

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