get_user

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which fully cover safety and behavior. The description does not add any behavioral details beyond the action, but it also does not contradict the annotations. It could mention that the tool is a simple, safe retrieval.

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 concise sentence that immediately states the verb, resource, and identifier. There is no unnecessary information, and it is front-loaded for quick understanding.

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 (1 parameter, no output schema, rich annotations), the description covers the core action. However, it is slightly incomplete as it does not specify what information is returned (e.g., user object with fields). For a simple retrieval, it mostly suffices.

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 already describes the single 'id' parameter as 'Entity ID (positive integer)' with 100% coverage. The tool description does not add any further meaning or context to the parameter, such as where to find the ID or that it's the user's unique identifier. Baseline of 3 is appropriate.

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 specific user by ID', which is a specific verb and resource. It effectively distinguishes this tool from sibling tools like list_users (which retrieves multiple users) and other get_ tools that target different entities.

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 when you have a user ID and need user details. However, it does not provide explicit guidance on when not to use it (e.g., when to prefer list_users) or mention any prerequisites or alternatives. Minimal but adequate.

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