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

No annotations are present, so the description carries the full disclosure burden. It adds a clear auth requirement (Bearer API key or OAuth token) and lists what the returned passport contains. It does not discuss errors or side effects, but the term 'Fetch' implies read-only behavior and the auth/contents details are substantive.

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 concise, front-loaded sentences deliver purpose, scope, and auth requirements without filler. Every sentence contributes useful information.

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?

Given there is no output schema and no annotations, the description provides a strong basis for invocation: purpose, intended agent population, auth method, and return-content highlights. It is missing explicit response structure and error behavior, but for a one-parameter fetch this is nearly complete.

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%, and the description only implicitly relates agent_id to the agent whose passport is being fetched. It gives no format, example, or additional constraints. For a single obvious string parameter this is adequate, but it adds little beyond the schema itself.

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: 'Fetch an OFF-platform agent's passport' and enumerates its contents (DID identity, provenance, verification tier, control-verified flag, reputation). The 'OFF-platform' qualifier clearly distinguishes this from sibling tools like get_agent.

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?

It gives an explicit use condition: 'Use for agents registered on NovaRail but hosted elsewhere.' This tells an agent when to select the tool, though it does not name the alternative tool or state a when-not-to-use case.

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