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

No annotations are provided, so the description carries the full burden. While it clarifies that the operation is a retrieval ('Get') and the output is a signed, portable credential, it does not disclose potential prerequisites (like authentication), side effects, error conditions, or rate limits. For a tool that issues credentials, more transparency is needed.

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?

The description is a single, concise sentence that leads with the action and key artifact. All words contribute meaningful information, and there is no redundancy.

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?

The description provides a clear sense of the return value (a signed, portable W3C Verifiable Credential), and the single-parameter schema is simple. However, the lack of an output schema and absence of any note about prerequisites or error handling makes it slightly under-specified for a tool in a security-sensitive domain.

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?

The input schema fully documents the single parameter, node_id, with a clear description ('Your OracleNet node ID or DID'). The tool description adds no additional param-specific meaning, but since schema coverage is 100%, a baseline of 3 is appropriate.

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 uses the specific verb 'Get' with the resource 'Trust Passport (W3C Verifiable Credential)' and specifies the context 'proving your trust level in OracleNet.' This clearly distinguishes it from sibling tools like quantum_status or quantum_scan.

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 implies the tool should be used when a user needs a verifiable trust credential, but it does not explicitly state when to use it over alternatives or identify any exclusions. With many sibling tools, more explicit guidance would be beneficial.

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