get_user

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

No annotations are provided, so the description bears full burden for behavioral disclosure. It only states 'Get detailed information' without mentioning whether the operation requires authentication, what happens if the user does not exist, or any side effects. The return value is vaguely described as 'User details'.

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 very short, with the main purpose front-loaded. The Args/Returns section is somewhat redundant with the schema but acceptable. No unnecessary words. Slightly more structure could be achieved by eliminating the docstring format, but it remains concise.

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 that an output schema exists (though not shown), the description need not detail return values. However, the tool lacks any error handling notes or behavioral context (e.g., read-only, auth required). For a simple data retrieval tool, the description is minimally complete but could be more informative.

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 input schema has one parameter (user_id) with 0% coverage. The description adds 'The ID of the user' which clarifies the parameter's purpose but offers no additional details like format or constraints. This is adequate for a single, obvious parameter but does not exceed baseline expectations.

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 that the tool retrieves detailed information about a specific user, using a verb+resource structure. It distinguishes itself from sibling tools like 'list_users' (which retrieves all users) and other resource-specific get tools.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context for use, or exclusions (e.g., when to use 'get_user' vs 'list_users' or other get tools).

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