get_user

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

Given no annotations are provided, the description solely bears the burden of behavioral disclosure. It correctly implies a read-only, non-destructive operation, but does not mention any behavioral details such as input precedence (which identifier takes priority when multiple are given), error responses, or performance considerations.

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 extremely concise with only two sentences, no redundancy, and front-loaded with the core purpose. Every sentence serves a purpose.

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 has 6 parameters, no output schema, and no annotations, the description is somewhat underspecified. While the purpose and basic constraint are clear, the lack of return value or behavior details (e.g., what user info is returned, what happens for ambiguous matches) leaves gaps for an AI agent to potentially misuse the tool.

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 description coverage is 100%, so the schema fully documents each parameter. The description adds value by explicitly stating the minimum contract ('at least one identifier'), which is not encoded in the schema structure (no required fields). This compensates for the schema's lack of a validation rule.

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 resource 'user information', and specifies that it operates by 'various identifiers', distinguishing it from sibling tools like create_user or delete_user. However, it does not explicitly differentiate it from search_users, which might also return user info by criteria.

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 includes a necessary constraint ('At least one identifier must be provided'), which guides usage by preventing invalid calls. However, it provides no guidance on when to use this tool versus alternatives like search_users, or when to prefer one identifier over another.

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