sw_get_current_user

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

Annotation readOnlyHint=true already establishes safety; the description adds behavioral detail by naming the exact return fields (id, first_name, last_name, email) and clarifying that the id is used for expense splits. It doesn't discuss errors or rate limits, but with the read-only annotation covering safety, this is sufficient.

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 concise sentences: the first states purpose and return fields, the second provides a usage guideline. No 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?

For a zero-parameter read-only profile tool, the description covers what it does, what it returns, and a practical application. Absence of an output schema is mitigated by listing the fields. It's fully complete for the tool's complexity.

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 tool has zero parameters, so the description cannot add parameter semantics. The baseline for zero-param tools is 4, and no compensation is needed.

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 specifies a clear action ('Get the authenticated Splitwise user's profile') with explicit fields (id, first_name, last_name, email). The term 'authenticated' distinguishes it from sibling sw_get_user, which likely retrieves other users' profiles, and the sentence about building custom expense splits reinforces its role.

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 explicit context for when to use it: to obtain the current user's id for building custom expense splits. It doesn't explicitly exclude alternatives, but the use case is clear enough, earning a 4 for clear context without exclusions.

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