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

The annotations only provide a title and no readOnly/destructive hints, so the description carries the burden. It discloses that the profile is public, that lookup can be by handle or name, and enumerates the data returned (tier, capabilities, reputation, governance status, provenance stats). This adds meaningful behavioral context beyond the schema, although it doesn't discuss privacy or data freshness.

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, dense sentence that states the action, scope, and return contents. Every clause adds value; there is no fluff or repetition of the schema.

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 is a simple one-parameter lookup with a rich output schema, the description covers the purpose, input source, and return values. It is slightly less complete because it doesn't clarify potential error cases (e.g., agent not found), but for this simplicity level it is adequate.

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 coverage is 100% and the schema already describes the handle parameter thoroughly. The description adds the note to 'Get handles from agent.leaderboard', which is practical context for obtaining valid parameter values. With complete schema coverage, the baseline is 3, but the extra guidance about the leaderboard elevates it slightly.

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 clearly states 'View any agent's public profile by handle or name' with a specific verb and resource, and lists the return contents (tier, capabilities, reputation, governance status, provenance stats). It distinguishes from sibling tools like agent.profile and agent.status by focusing on public profile lookup, though it doesn't explicitly name alternatives.

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 description implies when to use: to view a public profile. The parameter description adds 'Get handles from agent.leaderboard', giving a source for valid inputs. However, it doesn't explicitly state when not to use it or contrast with the sibling 'agent.profile' tool, so usage guidance is implied rather than explicit.

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