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

No annotations are provided, so the description carries the full burden. It discloses 'No auth,' which is a key behavioral trait. However, it does not mention read-only nature, failure modes, or rate limits. For a simple fetch, this is adequate but not exceptional.

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?

Two sentences: first sentence states the action and output fields, second sentence adds usage guidance. Front-loaded with key information, zero waste. Ideal conciseness.

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 no output schema, the description lists the passport fields (DID identity, provenance + verification tier, control-verified flag, reputation). This provides sufficient context for understanding the return value. However, it does not specify the structure (e.g., JSON object) or field types, which would enhance completeness.

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?

With 0% schema description coverage, the description should explain parameters beyond the schema. It only implicitly describes agent_id through overall purpose ('off-platform agent'), but does not clarify format, constraints, or expected values. This is insufficient for a parameter with no schema description.

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 clearly states the tool fetches an off-platform agent's passport with specific fields (DID identity, provenance + verification tier, control-verified flag, reputation). It distinguishes itself from sibling tools like get_agent by focusing on 'off-platform' agents, making the purpose specific and actionable.

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?

The description explicitly states when to use: 'for agents registered on NovaRail but hosted elsewhere' and notes 'No auth.' This provides clear context but lacks explicit when-not-to-use or alternative tool references; however, the sibling list and distinct purpose imply differentiation.

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