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

Annotations already declare the safety profile (non-read-only, non-idempotent, non-destructive, closed-world), and the description adds the POST route and the shape of the returned state (scope/subject/expiry), which is genuinely useful with no output schema. It does not explain why verification is flagged non-idempotent, nor any auth or rate-limit behavior.

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 well-formed sentence that front-loads the verb and resource before the return values and route. No redundant or filler text, though the parenthetical route is arguably metadata rather than definition.

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 verification call with no output schema, the description usefully enumerates the return fields and the HTTP route. It still omits how the credential is supplied in the body and any auth or failure-state context an agent would need to call it 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?

Only one optional 'body' parameter and schema coverage is 100%, so per the rubric the baseline is 3. The description confirms the endpoint but adds no detail on what the body must contain (the credential itself?), leaving the schema's pointer-style body description to carry the load.

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?

Specific verb 'Verify' plus a precisely named resource, 'AffixIO agent-trust credential', with the returned fields (scope, subject, expiry) spelled out. This distinguishes it from other verify siblings like affix_token_verify or affix_delegate_verify by resource, though it never explicitly contrasts with them.

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?

The description states what happens but gives no when-to-use context, no prerequisites (does a credential need to be enrolled first?), and no guidance on choosing this over affix_agent_trust_authorise, affix_gate_verify, or the other verify tools.

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