get_user

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

With no annotations, the description carries the full burden. It discloses that it returns a complete user record, lists the fields, and highlights the numeric Id requirement. However, it does not mention behavior on nonexistent extension (e.g., error handling). Otherwise clear.

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?

Two sentences plus a list of fields—no wasted words. The most critical usage instruction comes first. Every sentence is purposeful and adds value.

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 (single parameter, no output schema), the description is complete. It lists all return fields, explains the importance of the numeric Id, and provides usage context. No gaps for an agent to execute correctly.

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 has 100% coverage with a description of 'extension' as a string. The description adds meaning with examples ('e.g. 101 or 200') and explains the parameter's role in retrieving a single extension. This goes beyond what the schema provides.

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 tool fetches one specific extension by number, using a specific verb ('get') and resource ('user record'). It distinguishes from siblings like 'find_users' by emphasizing 'ONE specific extension' and explicitly mentions its role as a prerequisite for update/delete operations.

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?

Provides explicit guidance: 'Use this when the user asks about ONE specific extension by number' and 'Always call this before update_user or delete_user to get the Id.' This tells the agent exactly when to use it and when not (e.g., when listing multiple extensions, use find_users instead).

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