get_user

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

With no annotations, the description carries the full burden. It discloses that the tool 'Retrieves detailed information' and describes included fields and a JSON return format. However, it does not mention error handling (e.g., 404 for missing user), authentication requirements, or rate limits, leaving some behavioral gaps.

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 well-structured with a lead sentence, explanatory paragraph, Args/Returns sections, and an example. It is concise, though the first two sentences are slightly redundant ('Get a single user by ID' and 'Retrieves detailed information about a specific user').

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?

This is a simple one-parameter read tool with an output schema available. The description covers purpose, parameter meaning, return format, and an example. It is fully adequate for an agent to decide when to use it and how to call it correctly.

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 provides only the parameter name and type (integer), with 0% description coverage. The description's Args section explains 'user_id: The AgencyAnalytics user ID' and provides an example (456), adding the domain meaning that the schema lacks. This effectively compensates for the low coverage.

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 'Get a single user by ID' and elaborates with 'Retrieves detailed information about a specific user including their role, status, and campaign access.' This distinguishes it from sibling tools like list_users (multiple users) and update_user/delete_user (mutations), using a specific verb, resource, and scope.

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 clearly implies the tool should be used when you have a user ID and need detailed info on that single user. It provides clear context but does not explicitly mention alternatives like list_users or state when not to use this tool, so it lacks explicit exclusions.

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