get_me

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Gets information' clearly signals a read-only operation, but the description does not mention authentication failure behavior, rate limits, or what fields are returned. It is adequate but not deeply transparent.

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, front-loaded, concise sentence with no filler. It directly states the action and the target resource, and every word contributes meaning.

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 zero-parameter read-only tool, the description names the target resource and implies safe reading. However, with no output schema and no annotations, the word 'information' is vague: an agent cannot anticipate the exact response shape or whether specific fields like bot user ID, username, or avatar will be present.

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 has zero parameters and 100% schema description coverage, so there are no parameter semantics for the description to add. The description nevertheless clarifies that the call is scoped to the authenticated bot user, which is the only context an agent needs for a no-argument call.

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 uses a specific verb ('Gets information') and identifies the exact resource ('current authenticated Discord bot user'), which clearly distinguishes it from sibling tools that operate on guilds, channels, messages, and reactions. No ambiguity remains about what the tool does.

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 the tool is for retrieving data about the bot's own identity; no sibling tool targets the bot user itself, so the intended use is fairly evident. However, it does not explicitly state when to prefer this over alternatives or provide exclusions, so guidance is implied rather than fully stated.

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