get_user

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention whether the operation is read-only, what the return format is, or what happens if the user is not found. The bare 'Get a user by ID' offers no context about side effects, permissions, or error behavior.

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, compact sentence: 'Get a user by ID.' It is appropriately sized for the tool's simple functionality and contains no unnecessary words or repetition.

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?

Given the tool's simplicity, a complete description would at least mention that it returns a user object and possibly note behavior for nonexistent IDs. The current description omits any return information or edge cases, relying entirely on the tool name for context. There is no output schema to fill this gap.

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 required integer 'id' with 0% description coverage. The description merely repeats the concept of 'by ID' without adding meaning such as the ID's purpose, format, or range. It does not compensate for the lack of parameter documentation.

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 'Get a user by ID' clearly states a specific action (get) on a specific resource (user) with a specific method (by ID). This distinguishes it from sibling tools like list_users, which retrieves multiple users, and other getters for different resources.

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 usage: use this tool when you have a user ID and need the corresponding user record. However, it provides no explicit guidance on alternatives or when not to use it, such as when you need to list all users or fetch a different resource.

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