discord_whoami

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

No annotations are provided, so the description carries the full burden. It conveys that this is a passive read of the proxied account and what fields come back, but says nothing about auth requirements or whether the proxy connection must be established first, so behavioral coverage is only partial.

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?

Reasonably short and front-loaded, with the core purpose in the first sentence. The trailing "Returns: JSON object with the Discord account information" restates what the body already said and duplicates the output schema, adding minor redundancy.

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?

An output schema exists, so return values need no elaboration, and with no parameters there is little else an agent needs. The description is sufficient for a simple identity lookup, though it could have noted the auth/proxy prerequisite.

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 the baseline of 4 applies. There is no parameter ambiguity to resolve, and the description correctly indicates the call needs no input.

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 verb and resource ("Get information about the currently proxied Discord account") and enumerates the returned fields (username, ID, discriminator). It is clearly the identity-lookup tool among action-oriented siblings, though it never explicitly names or contrasts a sibling.

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?

Usage is implied by "currently proxied Discord account" - an agent can infer this reports the proxy's own identity - but there is no explicit when-to-use, prerequisites, or alternates. For a zero-parameter identity tool the implication is adequate, but no guidance is actually stated.

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