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 states what the tool does and that the result includes the site role, but it does not disclose potential error behavior, authentication requirements, or any side effects. The read-only nature is implied by 'get', and the description is not misleading, but it lacks explicit safety or limitation information.

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, short sentence (10 words) that directly states the core functionality. There is no redundancy, filler, or unnecessary detail. Every word contributes to the meaning.

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?

For a simple read tool with one parameter and an existing output schema, the description covers the essential purpose and a key output characteristic (site role). The output schema presumably details the return structure, so that is not a gap. However, it lacks any usage guidance or explicit read-only assurance, which prevents a perfect score.

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 one parameter, user_id, with no description (0% coverage). The tool description only says 'by id', which adds no meaning beyond the parameter name itself. It does not clarify the type or format of the id (e.g., UUID, email) or any constraints, so the description fails to compensate for the missing schema descriptions.

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 by id'), and adds a specific detail ('including their site role'). This distinguishes it from siblings like list_users (which lists all users), create_user, update_user, etc. The purpose is unambiguous and specific.

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 the usage: fetch a single user by id. It provides clear context for when to use this tool (when you need one user's details) without explicitly naming alternatives like list_users for fetching all users. There are no exclusions stated, but the scope ('single user') gives sufficient guidance.

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