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

The description adds real context beyond the annotations: it is 'read live ... on every call' and 'the first call issues version 1', which explains why readOnlyHint=false (a write side effect on first call) while idempotentHint=true. It does not discuss auth/permissions or failure behavior, but the annotation-consistent side-effect disclosure is valuable.

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?

Front-loads the return content, then the live-read/versioning behavior, then the parameter meanings. Dense but each clause earns its place; only the parenthetical GTIN explanation is slightly redundant.

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 return shape need not be explained, and annotations cover the safety profile; the description supplies the side-effect/versioning nuance and both parameter meanings. Only default-value and permission details are absent.

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 0%, so the description carries the burden and does document both params: subject is a GTIN of 8-14 digits or a market/banner string, and kind is 'gtin or banner (optional)'. It does not state what kind defaults to when omitted, a small remaining gap.

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+resource ('get the signed passport') and enumerates the payload it returns (holding hub, clearance, compliance records, listing, payment door). It is clear what the tool does, but it never names or distinguishes itself from the sibling list_passports or verify_passport.

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 only implied: retrieving the passport for a single subject ('a GTIN ... or market/banner'). There is no explicit when-to-use versus verify_passport or list_passports, and no statement of when this tool is not appropriate.

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