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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds value by listing specific returned fields (id, username, discriminator, avatar, etc.), giving the agent a clear idea of the response shape. No contradictions.

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 that is direct and information-dense. It includes the verb, resource, and examples of fields, with no filler. Perfectly concise.

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 simple read-only getter with no output schema, the description is mostly sufficient, but it omits any explanation of the 'account' parameter and any potential prerequisites (e.g., bot authentication). Given the tool's simplicity and the annotations covering safety, a score of 3 is appropriate.

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 schema has one optional parameter 'account' (string) with no description. Schema description coverage is 0%, and the description does not mention this parameter at all. The agent has no guidance on what 'account' refers to, whether it's required for multi-bot setups, or its format. This is a significant gap.

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 the tool returns the bot's own user profile with specific fields (id, username, discriminator, avatar). It distinguishes from sibling tools like discord_get_user, which would fetch other users' profiles.

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 it (when you need the bot's own profile) and implicitly differentiates from discord_get_user, but it does not explicitly state 'use this instead of discord_get_user' or list exclusions. Context is sufficient for a simple getter.

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