Get user

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

No annotations are provided, so the description carries the burden. It discloses the behavior that id=0 is not supported. However, it does not mention other behaviors such as authentication needs, error handling for missing users, or response format. The disclosure is minimal but accurate.

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?

Two sentences, no wasted words. Every sentence earns its place by stating the core function and a critical caveat. Front-loaded with the main action.

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?

The description covers the main functionality and a caveat, but lacks details about the expand parameter, potential errors, and differentiation from sibling tool npm_get_me. For a simple tool with no output schema, it is adequate but not complete.

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 50% (expand has a description). The description adds meaning to the id parameter by clarifying that 0 is not valid for 'me', which goes beyond schema's exclusiveMinimum. However, it does not explain the expand parameter, missing an opportunity to add value.

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 verb 'Get' and resource 'user by ID'. It also specifies a key nuance that 'Pass 'me' via id=0 is not supported; use the numeric ID.' This distinguishes it from sibling tools like npm_get_me.

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 provides a specific usage guideline regarding the id parameter (not using 0 for 'me'), but does not explicitly differentiate this tool from alternatives like npm_get_me or explain when to use which. It implies the context but lacks explicit guidance.

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