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

Annotations already declare idempotentHint=true and destructiveHint=false; the description's 'once' reinforces the idempotency and adds meaning beyond annotations by clarifying the effect is nonfinancial and carries no rankings or influence. It stops short of describing auth requirements or what the response looks like.

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 fragments with zero waste, and the core action is front-loaded before the qualifiers. It is terse and readable, though the second fragment is slightly clipped.

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 non-destructive mutation with no output schema, annotations cover the safety profile, but the 0% parameter coverage means the description should carry more of the load. It leaves the 'key' parameter and the exact mutation semantics unexplained.

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 schema documents neither parameter. The description implies contribution_id points at 'another participant's contribution' but never explains the 'key' parameter or the integer minimum on contribution_id, leaving half the parameters undocumented in both places.

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?

States a specific verb+resource: 'Acknowledge another participant's contribution.' An agent can tell this is an acknowledgement action, distinguishing it from the many read_* siblings. However, it does not explicitly contrast itself with nearby write siblings like contribute or submit_feedback.

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?

'Nonfinancial; no rankings or influence' implicitly bounds what this tool is for and signals it is distinct from a monetary contribute action. But there is no explicit when-to-use or when-to-prefer-an-alternative guidance, and no prerequisites are stated.

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