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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, which tells the agent this is a non-idempotent write. The description adds only the HTTP path and nothing about what a 'token carrier' is, whether issuing requires authentication, token lifetime, or what a repeated call does. Given annotations carry the safety profile, the description contributes almost no additional behavioral context.

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 short sentence with the purpose front-loaded and the endpoint parenthetically appended; nothing is redundant. It is efficient, though the brevity is partly under-specification rather than disciplined editing.

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 mutating tool with no output schema, the definition omits what the returned token is used for, required body fields, auth expectations, and how the result feeds affix_token_verify. An agent could call it, but only by guessing at the request contract.

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?

There is a single optional 'body' parameter with 100% schema description coverage, so the baseline is 3. The description adds no parameter meaning at all, and the schema's own body description merely points to an external OpenAPI resource rather than documenting the contract inline.

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 (issue) and resource (verification token carrier) and even names the underlying endpoint (POST /v1/token/issue), so the operation is identifiable. It does not explicitly contrast itself with the sibling affix_token_verify, though the issue/verify pairing is strongly implied by the names.

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 issue a token versus calling affix_token_verify, no prerequisites (auth, prior enrolment, caller identity), and no stated conditions or exclusions. The agent must infer usage entirely from the tool name.

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