get_user

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

The operation is a simple get (read-only). No annotations are provided, but the description implies no side effects. It does not mention permissions or errors, but for a get operation, the behavioral assumptions are 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?

The description is extremely concise: one sentence and a parameter format. Every word is necessary and front-loaded.

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 presence of an output schema, return values are covered. The parameter is well explained. Missing error handling info (e.g., if user not found) but overall adequate for a simple get 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?

The schema has 0% description coverage for the parameter. The description compensates by specifying the format 'user@realm' and providing an example 'admin@pam', adding significant meaning beyond the schema.

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 details for a specific user.' This is a specific verb and resource, distinguishing it from siblings like 'list_users' (get all) and 'create_user' (create).

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 provides the format for the userid parameter but does not explicitly state when to use this tool versus alternatives like 'list_users' or 'get_user_token'. The context is implied but not explicit.

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