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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. Even so, the description adds zero behavioral detail: it does not say whether issuance requires prior authentication/enrolment, whether the resulting proof is single-use or how long it lives, or what triggers failure. For a state-creating POST tool this is a meaningful gap.

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?

One front-loaded sentence with no filler; the endpoint is a useful anchor. It is efficient, though the extreme terseness leaves useful space unused for a mutation tool.

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?

No output schema exists, so the description should describe what issuance returns (proof format, identifiers, expiry) and how to use it — it says nothing. With no usage context and no return-value explanation for a POST operation, the definition is too thin for an agent to call 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?

There is a single `body` parameter with full schema description coverage, so the schema carries the contract (deferring to the AffixIO OpenAPI resource). The description adds no parameter meaning beyond what the schema provides, which is the baseline-3 case when coverage is high.

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 ('Issue') and resource ('delegated-authority proof') plus the underlying endpoint, which is enough to distinguish it from sibling verbs like affix_delegate_verify. It does not, however, explicitly contrast itself with siblings such as affix_token_issue or affix_agent_trust_authorise, so differentiation is only implied by the resource name.

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 when-to-use guidance, no prerequisite or ordering information, and no mention of the obvious alternative affix_delegate_verify (the natural counterpart for checking such a proof). The agent must infer the correct context 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.