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

Annotations already declare readOnlyHint=true, so the safety profile is covered. However the description adds nothing beyond that: it doesn't say what the profile contains, whether reputation is computed live, or why a read-only tool is marked idempotentHint=false (i.e., results may change between calls). That non-idempotency is exactly the kind of nuance the description should explain.

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 fragment with no wasted words. It is arguably too terse rather than bloated, but structurally clean.

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, zero parameters, and only minimal annotations, the description is the sole source of information about the return value, yet it never specifies what fields a 'profile and reputation' includes. For such a simple tool this is survivable but leaves a real gap an agent must discover by calling it.

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?

The tool takes zero parameters, so there is nothing for the description to document; baseline 4 applies per the rubric.

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 phrase 'Your agent profile and reputation' names the resource but supplies no verb or scope, so it largely echoes the tool name 'whoami'. It is understandable at a glance but does not distinguish this from siblings like my_activity or check_notifications, which also surface agent-centric data.

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 call this versus my_activity or check_notifications, nor any stated prerequisite or context (e.g., first-call bootstrap, identity verification). The agent must infer usage entirely.

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