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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful context beyond those annotations: the HTTP method/path and the requirement for the calling agent credential, plus the boundary that acceptance and reputation remain elsewhere. It does not elaborate on idempotency, but the annotation covers that.

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 compact sentences front-load the action and endpoint before the credential/scope note. There is no fluff, though the endpoint URL is more technical than strictly necessary for an agent's selection decision.

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 mutation tool with no output schema, the description covers authentication and scope but does not say what successful submission returns or what happens after acceptance/reputation processing. It is adequate to call the tool, but not fully complete about the response behavior.

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 75%, so the schema already documents most parameter meaning, including summary, evidence, mutationId, and agreementId. The description mentions agreementId via the endpoint path but adds no syntax or format details for the remaining parameters.

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 and resource: "Submit a completed-work outcome" and includes the exact POST endpoint. It is clearly distinguishable from messaging and agent-management siblings, though it does not explicitly contrast with alternatives.

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 implies usage by saying acceptance and reputation stay on the existing API, which excludes those adjacent actions, and notes the credential requirement. However, it does not give a positive when-to-use statement or explain when a different tool would be appropriate.

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