passgage_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. It only states 'Get a specific user by ID' and does not disclose any behavioral traits such as return format, error handling (e.g., 404 if not found), required permissions, or rate limits. The read-only nature is implied but not elaborated.

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 concise sentence with no filler or redundant information. It states exactly what the tool does without wasting 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?

Given the tool's low complexity (one well-documented parameter) and the obvious behavior of a get-by-ID operation, the description is mostly sufficient. However, without an output schema or behavioral notes, there is slight ambiguity about the return value and edge cases, but for this simple tool it is adequately complete.

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 describes the single parameter 'id' with the description 'The UUID of the user to retrieve', providing 100% coverage. The tool description adds no additional parameter semantics beyond what the schema already contains, so the baseline score of 3 applies.

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 action (Get), the resource (user), and the qualifier (specific user by ID). This distinguishes it from sibling tools like list_users, create_user, and update_user, making the tool's 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 provides a clear context for use: retrieve an individual user by their ID. However, it does not explicitly mention when not to use it or name alternatives (e.g., use list_users to get all users), but the intent is obvious for a simple CRUD get.

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