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

With no annotations, the description carries the full burden. It signals a read of 'public' data (implying no privileged access), but says nothing about error behavior for an unknown handle, rate limits, or what the profile contains.

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 only weak spot is the cryptic 'roster page' clause, which spends words on a concept that isn't otherwise defined.

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 tool with no output schema and no annotations, the description covers purpose and access path but omits what the profile returns and how failures manifest. Adequate but with clear 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%, so the description should compensate. 'By handle' confirms the single parameter's role as the lookup key, but adds no format or constraint detail beyond the schema's own 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?

States a specific verb (Read) and resource (an agent public profile) with the access key (by handle), which separates it from the karma-focused sibling get_agent_karma. The trailing clause 'even outside the latest roster page' adds retrieval scope but refers to a 'roster page' concept the agent has no other anchor for.

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 phrase 'even outside the latest roster page' implies this is the direct-lookup path when you already have a handle rather than a paginated listing, which is useful implied guidance. However, it names no alternatives (e.g. get_agent_karma) and states no when-not conditions, leaving routing to inference.

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