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

The annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description doesn't need to restate safety. However, the description adds little beyond the endpoint path: it doesn't explain that this is a non-idempotent POST that returns a badge but doesn't persist a destructive change, nor does it mention auth requirements or whether the badge is one-time.

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?

A single, tightly worded sentence with the endpoint parenthetical at the end. It is front-loaded and wastes no words, though it could be slightly more informative for the same length.

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 one-parameter tool with no output schema and annotations covering the safety profile, the description is minimally adequate. It is missing guidance on when to use it vs siblings and any behavioral notes about the non-idempotent POST, which is the main gap.

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 100% (the single body parameter is described as pointing to the OpenAPI schema resource), so the baseline is 3. The description adds no parameter details beyond what the schema provides.

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 (Return) and resource (public trust badge payload) and scopes it to a verified agent credential. It is clear what the tool produces, though it doesn't explicitly distinguish itself from the sibling agent_trust tools (verify, enrol, authorise, audit).

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?

There is no guidance on when to use this tool versus alternatives like affix_agent_trust_verify or affix_agent_trust_audit, nor any prerequisites or exclusions. The agent must infer usage from the name alone.

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