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

Annotations already indicate a destructive, idempotent mutation, and the description adds meaningful behavior beyond that: human approval is separately required and the agent must never access the mailbox to obtain the code. This gives the agent an actionable guardrail for a side-effecting email operation. The reference to 'this code' is ambiguous, but it does not contradict the annotations.

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?

Three short sentences front-load the core action and then add the two most important guardrails: mandatory human approval and the prohibition on mailbox access. This is economical and well structured. The cryptic 'this code' phrase costs a point because it assumes context the agent does not have.

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, idempotent mutation with four required parameters and no output schema, the description does not say what the caller should expect in return, how to obtain the reviewer's verified email or the code, or how this tool relates to the other promotion siblings. It provides valuable safety context but leaves the agent without enough information to invoke the tool fully confidently.

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 coverage is only 50%; projectId and idempotencyKey are well documented, but entryId and revision are only regex patterns with no meaning explained. The description lists the content to send but does not map that content to any parameter or explain how the required entryId/revision relate to it. The tool description therefore does not compensate for the missing parameter documentation.

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 concrete action: send the exact reusable answer, proof references, owner, validity, and reuse scope to the reviewer's verified email, which clearly identifies a promotion-request operation. The 'separate human approval' condition helps distinguish it from confirmation/application siblings. It is slightly indirect about naming the library-promotion resource, but the tool name and email-send action make the purpose clear.

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 description implies when to use this tool by noting that human approval is mandatory even if the source dossier was already approved, and it warns against retrieving the code from the mailbox. However, it never explicitly names alternatives such as apply_library_promotion or confirm_library_promotion or states the conditions that should select this tool over them. Usage guidance is present but mostly implicit.

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