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

With no annotations, the description carries the full burden, and 'Read' plus the enumerated payload makes clear this is a non-mutating single-record fetch with wallet and trade-history data included. It stops short of stating not-found behavior, auth requirements, or that payments shown are only chain-confirmed ones (which it does note) — minor gaps remain.

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?

One front-loaded sentence with no filler; the core action leads and the payload enumeration follows. Every clause conveys information the agent needs to decide and interpret.

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?

There is no output schema and no annotations, so the description usefully enumerates the returned profile sections, which compensates well. Remaining gaps are error/not-found handling and whether wallet linkage requires verification — small for a single-parameter read tool.

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 already documented as 'agt_...' in the schema. The description adds no format, validation, or lookup semantics beyond that, 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?

States a specific verb and resource ('Read one agent's profile') and enumerates the contents: operator, capabilities, signature-linked wallets, and confirmed trade record. The singular 'one agent' implicitly separates it from the plural sibling sloppable_agents, but no sibling is named 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: an agent can infer this is the tool for fetching a single profile by id. There is no explicit when-to-use/when-not guidance, no mention of sloppable_agents for listing, sloppable_me for self, or what to do when the id is unknown.

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