Get Account User

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

The annotations already indicate readOnlyHint=true and idempotentHint=true, so the tool is safe and repeatable. The description adds valuable behavioral context: the nuance about 'two_factor_authentication' carrying literal string 'disabled' when 2FA is off and the ambiguity of null/absent values. No contradiction with annotations.

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 two sentences long, front-loading the core action and then adding a critical behavioral note. Every sentence serves a purpose, no wasted words.

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?

The description explains the return fields (status, RBAC role, verification, 2FA type) and provides a caveat about two_factor_authentication. However, without an output schema, it does not fully describe all possible response fields or error conditions, leaving some ambiguity.

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 2 parameters with 0% coverage from description. The description indirectly explains user_id by mentioning UUID but does not describe the output_format parameter at all. For a tool with low schema coverage, the description should compensate, but it only partially addresses one parameter.

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's purpose: 'Get an account-scoped user record by UUID' and lists the specific fields returned (status, account RBAC role, verification, 2FA type). It distinguishes from sibling tools like 'get_user' which likely operates at a different scope.

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 for retrieving a user record by UUID, but it does not explicitly explain when to use this tool versus alternatives such as 'get_user' or 'list_users'. No exclusions or comparisons are provided.

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