Get user

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

The description states it 'fetches' a user, implying a read-only operation with no side effects. However, with no annotations provided, it does not disclose error handling (e.g., missing id), permission requirements, or response format. This is acceptable for a simple get operation but lacks depth.

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, front-loaded with the verb 'Fetch', and no unnecessary words. It is optimally concise for the information it provides.

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 tool's simplicity (2 parameters, no annotations, no output schema), the description should mention the optional 'raw' parameter and hint at the return value or behavior. It does not, leaving gaps for the agent.

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 description mentions 'by numeric id', which adds some context to the required 'id' parameter, but it does not explain the optional 'raw' boolean parameter. Since schema description coverage is 0%, the description fails to compensate by explaining all parameters or their usage.

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 action (Fetch), resource (user), and method (by numeric id). It distinguishes from siblings like op_current_user and op_list_users by specifying the id-based retrieval.

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 it is for retrieving a single user by its numeric id, but it does not explicitly state when to use this tool versus alternatives like op_current_user (for current user) or op_list_users (for all users). No guidance on when not to use it.

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