get_user

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

No annotations are provided, so the description carries the full burden. It only says 'get user details' without disclosing potential side effects, permissions, rate limits, or behavior on missing/invalid IDs. For a read operation, it is minimally transparent but lacks context beyond the obvious.

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 one short sentence, immediately front-loaded with the core action and resource. It is appropriately sized for a simple get operation and contains no filler.

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 low complexity (one parameter, no output schema), the description provides the essential purpose but lacks usage guidance and behavioral context. It is adequate for a trivial get but leaves gaps around when to use and potential error handling.

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 parameter 'user_id' with 0% description coverage. The description mentions 'ID' but adds no new meaning beyond what the schema already shows—it does not clarify the expected format, constraints, or how the ID relates to the user. The description merely echoes the schema field.

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 the resource 'user details', with the ID as the key parameter. It distinguishes from sibling 'list_users' by indicating a specific ID-based retrieval, but does not explicitly name alternatives.

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 offers no explicit guidance on when to use this tool versus alternatives like list_users. It implies you need an ID, but does not state when this tool is preferred, any prerequisites, or exclusions.

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