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

The annotations already cover read-only, idempotent, open-world, non-destructive behavior. The description adds meaningful context beyond those: it is a public GET endpoint, returns display name, avatar URL choices, and scores, and explicitly carries no secrets.

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 sentence front-loads the resource, endpoint, returned fields, and safety note. It is appropriately sized with no filler and no repetition of the tool name.

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-only tool with rich annotations and no output schema, the description is nearly complete: it explains the public nature, the GET method, the returned data categories, and the no-secrets constraint. It lacks only explicit guidance about when to prefer this over sibling profile tools.

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 only parameter's schema description already states 'Public EVM or Solana address. Never a key or seed.' The tool description reinforces the wallet context but does not add format or syntax details beyond the schema.

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 resource and operation through 'Public game/profile card for a wallet (GET /api/game/me)' and names the returned fields. It is clearly a read, which distinguishes it from sibling write tools like set_profile and set_avatar, though it does not explicitly name an alternative.

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 explicit when-to-use guidance or routing to related tools. The phrase 'Public game/profile card' and 'No secrets' imply that it is for public profile data only, but no conditions or alternatives are stated.

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