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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine behavioral value by inventorying the returned data ('USDC settlement evidence', 'trust score'), though it says nothing about response shape, pagination, or freshness/latency of the indexer.

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?

A single front-loaded sentence with no filler; the verb+resource leads and the payload inventory follows. Every clause carries information.

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 correctly compensates by listing what the record contains. With one fully documented parameter and complete safety annotations, the only remaining gap is sibling routing and any note on data staleness, which is minor for this simplicity 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 agent_id parameter is documented in the schema as the ERC-8004 token ID in the Identity Registry. The description adds only 'for one agent', which conveys cardinality but no formatting or lookup semantics beyond the schema, so the 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?

The description gives a specific verb/resource ('Full ArcID record for one agent') and enumerates the payload (profile, owner, wallet, reputation, validations, trust score, settlement evidence). This implicitly distinguishes it from narrower siblings like get_agent_feedback and get_agent_validations by signalling a complete record, but it never names those alternatives 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?

Usage is only implied: the tool takes one agent_id and returns that agent's full record, so an agent can infer it is the lookup-by-ID entry point. There is no statement of when to prefer it over search_agents (discovery) or the focused feedback/validations tools, and no prerequisites are mentioned.

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