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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds only two bits beyond that: the $0.75 USDC cost and a hint that the result carries a `breaking_hop` and a `cited` flag. It says nothing about what happens on an incomplete chain, how ambiguity is resolved, or the cost/charge semantics (per call vs per hop).

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?

Short, but the second sentence is a run-on that mashes routing guidance, a return-value aside, and a price into one clause with broken grammar ('for consent chain, not json schema; an object with 24 fields...'). The purpose is front-loaded, so it is usable, but the structure is sloppy rather than tight.

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?

Output schema exists, so the '24 fields including breaking_hop, cited' note is redundant, and the cost disclosure is welcome. The gap is input-side: with generic parameter descriptions, nothing tells an agent what a valid hop object looks like or whether `hops` may be empty given 0 required params. Adequate but leaves a real invocation risk.

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 nominally 100%, but the parameter descriptions are pure boilerplate ('The hops this operation operates on. See the schema for its type...'), which tells an agent nothing. The tool description does not compensate by explaining the shape of a hop, whether `hops` is ordered, or how `subject_id` relates to it. Baseline 3 for high coverage, no credit earned.

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?

States a concrete verb chain (walk a chain, judge each hop) over a named resource (consent chain), which is far more specific than most siblings. It also pre-empts confusion with `clean_json_schema`, so an agent can tell the two apart without opening schemas. Slight deduction because 'the use' and 'permitted' are left undefined.

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?

Explicitly names the alternative and the selection rule: use this rather than `clean_json_schema` when the input is a consent chain, not a JSON schema. It gives no when-not conditions beyond that (e.g. what to do when the chain is malformed or a hop is missing), so it stops short of full guidance.

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