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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value beyond that: it is free and needs no key, it names the exact set of policy dimensions evaluated, and it discloses that the outcome is allow/deny accompanied by reasons. It says nothing about rate limits or what happens on a malformed token, but the core behavior is well disclosed.

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 trigger condition is front-loaded in the first sentence, and no sentence is filler. The long parenthetical list of policy fields makes the final clause a dense run-on that is harder to scan than it needs to be, which keeps it short of a 5.

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 an output schema present, the description needn't explain return values, and it correctly focuses on inputs and decision logic. For an 8-parameter tool with a nested policy object and zero required parameters, it covers the multi-signal evaluation well. The remaining gap is that it doesn't say which parameters form the agent-gate path versus the upload path (asset_sha256).

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?

Schema coverage is 75%, and the description meaningfully extends it by enumerating the contents of the opaque nested "policy" object (min_kya_level, require_kya, require_web_bot_auth, allowed_signature_agents, require_receipt, allow_agents, deny_agents, require_clearance, require_intent, max_intent_risk), which the schema itself does not detail. It also clarifies that "agent" may be a handle and that "request" carries the signature and intent-token key binding. It does not explain when asset_sha256 or clearance are needed.

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-and-resource: it evaluates an RS-KYA token, Web Bot Auth signature, Rights Receipt, clearance and intent token against a site policy and returns allow/deny with reasons. That is far more precise than the name alone. It doesn't explicitly distinguish itself from siblings like kya_check or kya_verify, so the differentiation is left to inference.

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?

"Call when your site accepts agents or uploads" gives a clear trigger condition for invoking it. However, with fifteen-plus siblings including kya_check, kya_verify, kya_lookup and verify_rights_manifest, there is no statement of when NOT to use this tool or which sibling handles a narrower single-signal check.

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