get_user

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

No annotations are provided, so the description carries full burden. It only states 'Gets details' and the API version, without disclosing behavioral traits such as authentication needs, rate limits, or the nature of the returned data. As a simple read operation, minimal transparency is acceptable but still insufficient.

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 sentence, concise and without extraneous content. However, the '[Tool Role]' prefix is unnecessary and could be omitted for even cleaner structure.

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 tool has an output schema (details not shown), but the description provides no information about the return value or what 'details' include. With 0% schema description coverage and one required parameter, the description is insufficient for an agent to use the tool correctly without additional knowledge.

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 description coverage is 0%, meaning the description must add parameter meaning. However, the description does not mention the 'username' parameter at all, only 'specific user'. The agent cannot infer the required parameter name from the description alone.

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 it gets details of a specific user, using a specific verb and resource. The mention of 'v1 API only' distinguishes it from potential other user tools. Sibling tools include 'list_users', confirming it's for a single user.

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 mentions 'v1 API only', providing some context, but does not explicitly state when to use this tool versus alternatives like 'list_users'. There is no exclusion or prerequisite guidance, leaving the agent to infer usage from sibling tool names.

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