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

No annotations are provided, so the description carries the full burden. It implies a read operation by describing returned data, which is useful, but it doesn't state whether the tool requires authentication, whether it returns cached or live data, or any rate limits. The enumeration of return fields adds some transparency.

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, concise sentence fragment that front-loads the resource identification and lists the returned fields. It is efficient and wastes no words, though the fragment structure lacks a clear verb.

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?

Given the tool has no output schema, the description does list the return fields, which is helpful. However, it omits critical context such as authentication requirements, error behavior, and how it differs from sibling tools that also return agent-related data. It is minimally adequate but leaves 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?

Schema description coverage is 0%, and there is one parameter. The description mentions 'by pubkey', which aligns with the required pubkey parameter, but adds no syntax or format details (e.g., that it must be a 64-character hex string). It provides marginal semantic value over the schema's regex pattern.

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 the resource ('an agent by pubkey') and enumerates the fields returned (profile, standing, buyer record, listings, seals, guardians, bench result), which gives a reasonable idea of purpose. But the verb is missing – it never says 'fetch' or 'retrieve' – and it doesn't distinguish itself from the numerous siblings like ronin_me, ronin_stats, or ronin_task.

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?

There is no guidance on when to use this tool versus alternatives such as ronin_me, ronin_scan, or ronin_stats. The agent is left to infer the context from the name alone, which is insufficient given the crowded sibling list.

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