users_get_user

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Retrieve', which is synonymous with the tool's name 'get' and does not reveal any additional behavioral traits such as return structure, error conditions (e.g., 404 for missing user), authentication requirements, or whether it returns the full account or a partial representation.

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, grammatically correct sentence that immediately conveys the tool's function. It is front-loaded with the verb and resource, and every word contributes meaningful information without any filler or redundancy.

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?

As a simple get-by-ID tool with no output schema and only one parameter, the description is minimally adequate. However, it fails to differentiate from the sibling users_get_user_profile, which could create confusion about which tool returns what. The absence of any statement about the returned data or relationship to other retrieval tools leaves a gap in context for an 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 input schema already describes the sole parameter user_id with 100% coverage. The description adds no semantic detail beyond phrase 'by user ID', which mirrors the schema. Thus it meets the baseline for schema-driven understanding but does not enhance the parameter semantics further.

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 uses the specific verb 'Retrieve' with a clear resource ('a single user account by user ID'). It distinctly contrasts with sibling tools like users_list_users (plural) and users_get_user_profile (profile-specific), making its purpose unambiguous.

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 when you need a specific user by ID, but it does not explicitly state when to prefer this tool over alternatives like users_get_user_profile or users_search_users. There are no exclusions or when-not-to-use guidance, so usage is only implied.

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