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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is covered without description help. The description adds useful context by describing the return as a signed binary result with a proof receipt, but it omits side effects (e.g. whether a receipt record is persisted for affix_verify_receipts), auth requirements, and quota/rate limits.

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 sentences, front-loaded with the action and followed by the endpoint and pointer to policy values. No filler, though the endpoint/policy note is dense and could be separated for scanning.

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?

With no output schema the description does explain the result shape (signed binary result plus proof receipt), which is the main missing piece. But the request body contract is entirely offloaded to an external resource, and no prerequisites or policy-value semantics are described, leaving the agent under-informed for a non-idempotent POST.

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 at 100% schema description coverage, so the schema already documents it. The description adds only an indirect hint that policy values go in the body ('see /v1/verify/policies'), with the actual contract deferred to an external OpenAPI resource; this is baseline-level value.

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 gives a specific verb and resource: run an eligibility verification against the AffixIO API and return a signed binary result plus a proof receipt. It also names the concrete endpoint (POST /v1/verify), which grounds the purpose. It stops short of differentiating this from the many other verify tools (affix_verify_receipts, affix_aggregate_verify, affix_token_verify), so it is clear but not fully disambiguating.

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?

Usage is implied by the example ('e.g. over-18') and by the pointer to /v1/verify/policies for policy values, which tells the agent where to source inputs. However there is no explicit statement of when to use this tool versus the sibling verify/receipt/aggregate tools, nor any exclusion guidance.

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