identity_get

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

No annotations are supplied, so the description must carry the burden; 'Get' plus the field list makes clear this is a read of registry state. It does not say what happens when agentId does not exist, whether the call is free/gasless, or that wallet address is optional and often absent — 'if set' hints at the last point but nothing more.

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 first sentence is well front-loaded and the return-field sentence is useful. The trailing 'Tip: call earning_opportunities' is unrelated promotion that does not help an agent invoke this tool and dilutes the definition.

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?

For a one-parameter read with no output schema, the description supplies the key return shape (owner, URI, wallet) which is exactly what's needed. Missing only edge-case behavior on unknown agent IDs, which is a minor gap at this complexity level.

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 description coverage is 100% and the single parameter agentId is documented in the schema as 'Agent ID to look up'. The description adds no format, origin, or bounds context (e.g. that IDs come from identity_get_last_id / identity_register), so baseline 3 applies.

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?

Names a specific verb ('Get') and resource ('agent identity information from ERC-8004 identity registry'), and enumerates the returned fields (owner address, URI, wallet address). It is distinguishable from identity_get_metadata and identity_get_last_id by the field list, though it never names those siblings explicitly.

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?

No guidance on when to use this versus the adjacent identity_get_metadata / identity_get_last_id / identity_register tools. The only routing sentence points at a completely unrelated tool (earning_opportunities), which is promotional rather than usage guidance.

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