sw_get_user

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds no further behavioral details such as authentication requirements, error behavior, or data access restrictions. It simply restates the action without going beyond the annotation.

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 sentence of seven words, front-loaded with the verb and resource. It contains no waste, and every word earns its place. This is an exemplary concise description.

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-only tool with one parameter and no output schema, the description adequately specifies what it does and what input is needed. It implies the return value (the profile) and is sufficient for an agent to invoke it, though it could mention potential limitations (e.g., need for friendship) if any exist; it is not incomplete enough to warrant a lower 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?

Schema description coverage is 100%—the parameter 'id' is already described as 'User ID'. The description merely says 'by id', adding no semantic value beyond what the schema provides. Baseline of 3 applies because the schema fully documents the 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 action (Get), the resource (another Splitwise user's profile), and the required parameter (by id). It distinguishes from sibling tools like sw_get_current_user by specifying 'another', making the 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 clear context: it is used to fetch a user's profile by ID, and the word 'another' implies it is not for the current user (contrasting with sw_get_current_user). However, it does not explicitly exclude alternatives or state when not to use it, so it stops short of a 5.

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