sw_get_user

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds useful behavioral detail: the compact default merges first_name/last_name into name, while view:'full' keeps them separate. This goes beyond what the annotation alone provides.

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 efficient sentences with no filler. The core purpose is front-loaded, and the behavioral note about compact/full is placed immediately after, giving the agent the most important call-shaping information up front.

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 lookup with a detailed schema and readOnlyHint, the description plus schema is largely sufficient. It explains the response-shape distinction and required ID. It relies somewhat on the sibling reference for full shape understanding and omits error/not-found behavior, but those are minor for this tool.

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%, and the schema fully explains the id and view parameters, including the compact/full response shape. The description largely restates the view behavior already present in the schema, so it adds limited new parameter meaning.

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 states a specific verb and resource: 'Get another Splitwise user's profile by id.' It also distinguishes itself from the sibling sw_get_current_user by emphasizing 'another' user, making the target resource 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 clearly implies this tool is for fetching a different user's profile by ID, and references sw_get_current_user as a related alternative. However, it stops short of explicitly saying 'use sw_get_current_user for the current user' or providing when-not-to-use conditions.

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