get_passport

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

No annotations are provided, so the description bears the full burden. It indicates a read operation but does not disclose side effects, permissions, rate limits, or causal impact. The mention of Ed25519 signing describes content, not behavior.

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 sentence that is front-loaded with the verb and object, and efficiently conveys the key contents of the passport without unnecessary words.

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 tool lacks an output schema, so the description must explain return values. It lists contents (identity, stamp, etc.) but omits details about the structure, format of the signed data, or what 'cross-protocol' means. For a tool with one parameter, it is moderately complete but has gaps.

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 covers 100% of the single parameter (wallet_address) with a clear description. However, the tool description does not add extra meaning beyond what the schema provides, such as why the wallet_address is needed or its role in identifying the agent passport.

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 verb 'Get' and the object 'signed cross-protocol agent passport', and lists its contents (identity, stamp, reputation, A2A card, MCP metadata). This distinguishes it from siblings like get_agent (basic agent info) and get_agent_reputation (only reputation).

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 usage for obtaining a passport but provides no explicit guidance on when to use this tool versus alternatives like get_agent or get_verifiable_credential. No when-not-to-use or prerequisite information is given.

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