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

With no annotations, the description carries the full disclosure burden. It does usefully disclose the paid nature of the call ('Price: $0.01 USDC') and the shape of what comes back, but says nothing about whether the call fails or returns a neutral result for an unknown or unverified passport, nor about any auth or rate constraints.

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?

Three short sentences, front-loaded with the action and result, followed by the usage condition and the price. The phrase 'to assess reliability' is mildly redundant with 'trust score', but there is no padding worth cutting.

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 single-parameter, non-destructive read with no output schema, the description covers purpose, trigger, return fields, and cost. The main residual gap is failure/edge-case behavior for an unknown or unverified passport, which matters given the per-call fee.

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 one parameter with 100% schema description coverage, so the baseline is 3. The description adds only the framing that the ID belongs to a 'human trust passport' rather than an agent passport, which is a marginal but real semantic contribution beyond the schema text.

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 specific verb and resource ('Verify a human trust passport') and names the payload of the response (trust score, tier, verification status). It implicitly scopes to humans ('any human counterparty'), which hints at a distinction from the agent-facing pabandi_verify_passport sibling, but it never names that sibling outright.

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?

Gives a clear trigger condition: call it before booking or transacting with a human counterparty. It does not state when NOT to use it, nor does it route the agent to pabandi_verify_passport, pabandi_check_counterparty, or pabandi_verify_trust_attestation, which occupy adjacent ground.

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