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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds almost nothing beyond that: it does not explain what 'recovering context' returns, whether it touches shared state, or any auth/rate-limit behavior.

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?

It is short, but the two clauses run together without punctuation into a single malformed sentence, and the second clause references a nonexistent parameter, so the brevity reflects under-specification rather than efficient front-loading.

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 tool with 10 parameters, an output schema, and rich sibling competition, this two-clause description is far too thin. It leaves the agent unable to map any input parameter to a purpose and misdirects it toward a link_id that does not exist.

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?

There are 10 parameters at 0% schema description coverage, and the description documents none of them. Worse, it instructs the agent to use a 'link_id', which is not among the schema properties, actively misleading parameter selection.

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 verb ("Recover") and a set of resources ("mutation, task, approval, and policy context"), which is more specific than a tautology. However, "context" is undefined and there is no differentiation from close siblings like operations_get or operations_get_approval, so an agent cannot confidently tell what makes this tool distinct.

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 the workflow's original link_id when exposed" is the only usage hint, and it points to a parameter that does not exist in the schema. No alternatives (operations_get, operations_get_approval) are named, and no when-not-to-use guidance is given.

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