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

Annotations already mark the tool readOnly, idempotent, and non-destructive, but the description adds substantial behavior: deterministic execution, Cloudflare Worker vs browser compute modes, transient processing with no storage/logging/retention, AP2 artifact export with execution_hash, and FV-status receipt semantics. These disclosures go well beyond the annotations and do not contradict them.

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?

The description is front-loaded and information-dense but overly bloated: regulatory history, KYA-OS donation date, an open URL, upstream/downstream artifact lists, and FV-status verification details are not needed for selecting or invoking the tool. It also repeats compute-mode semantics that are already present in the input schema, making it longer than necessary.

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?

Despite no output schema, the description covers compute modes, data privacy/retention behavior, chaining inputs, output artifact type (AP2 with execution_hash), and provenance verification. It leaves the exact AP2 return structure implicit and relies on an external manifest for policy_parameters field names, but an agent has enough context to invoke it correctly.

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?

The schema already documents all four parameters (100% coverage), so the baseline is 3. The description adds useful behavior beyond the enum text by explaining the compute:"auto" default, gpu:false/gpu:true dispatch rules, and browser delegation URL behavior, though it adds little for parent_hashes and parent_tool_ids beyond what the schema already states.

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 title and opening phrase clearly identify the tool as an agent identity and authorization attestation checker within OpenChainGraph, and the compliance_mandate context gives a specific domain. However, it does not explicitly distinguish itself from sibling tools like check_agent_token_scope or verify_kya_x402_scope.

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 regulatory context implies use for EU AI Act Annex III high-risk agent attestation obligations, and the description gives a clear operational constraint ('Use synthetic or anonymised inputs only'). It never states when to prefer this tool over alternatives, when not to use it, or which sibling tools overlap with it.

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