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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the payload facets (a genuine plus given no output schema), and the noun 'passport' plus the get_ prefix implies a safe read, but it says nothing about permissions, caching, cost, or side effects.

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 dense sentences with no filler, and the content enumeration is front-loaded. The final clause adds intent rather than restating the name, though the phrasing is jargon-heavy and could be tighter.

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 no output schema, the description reasonably compensates by listing the return fields. However, it leaves the agent without guidance on when this is preferable to get_agent or get_autonomy, and without any note on safety or freshness, so it is adequate rather than 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?

The tool takes zero parameters, which is the baseline-4 case. The description adds no parameter meaning, but none is needed; there is nothing for it to clarify beyond the absence of arguments.

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 names a specific resource (the vault agent's passport) and enumerates its contents: identity, capabilities, machine surfaces (MCP/REST/OpenAPI), Autonomy Score, and on-chain decision receipt pointers. That is concrete enough for an agent to know what it retrieves, though it never distinguishes itself from the closely named sibling 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?

Usage is only implied by the closing clause 'Shaped so another agent can evaluate this one programmatically,' which suggests agent-to-agent discovery/evaluation. There is no explicit when-to-use, when-not-to-use, or routing versus get_agent or get_autonomy, both of which cover overlapping ground.

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