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

Annotations already provide idempotentHint=false and readOnlyHint=false, but the description adds valuable behavioral context: the call persists credential-use state, making it non-idempotent end-to-end, and includes a business-level replay guard (an already-retried block is not retried again). It does not contradict annotations. The additional detail about server-side derivation of eligibility, tenant, etc., also enhances transparency, though it doesn't explicitly mention destructive or safety implications beyond what annotations imply.

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 dense but efficient; it front-loads the primary purpose, then provides usage context, differentiation, and important behavioral caveats. Every sentence carries information, and it avoids redundancy. Slightly long, but each clause earns its place.

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?

The description covers the purpose, usage, distinction, and non-idempotency, and there is an output schema so return details are not required. However, it does not explain the role of decision_md, and the parameter name mismatch (task_block id vs escalation_id) is a potential source of confusion. It is mostly complete but leaves one parameter and naming consistency unaddressed.

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%, so the description must compensate. It explains that 'task_block id' should be passed (mapping to escalation_id), but it gives no information about the second required parameter, decision_md. It also uses a different name ('task_block id' vs 'escalation_id') which could cause confusion. The description adds minimal value for the parameters beyond what the schema already lists.

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 ('Grant one fresh attempt') and resource ('recovery-budget task block'), and explicitly distinguishes itself from 'resolve_escalation', making it clear what it does and how it differs from a sibling. The purpose is unambiguous and action-oriented.

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 explicitly tells the user when to use it: after fixing a recovery-budget task block. It also names the alternative (resolve_escalation) and clarifies that the alternative is acknowledgement-only, giving a clear routing decision.

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