splitwise_action

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

No annotations are provided, and the description does not mention behavioral traits like authentication (api_key parameter), side effects (e.g., create_expense creates data), rate limits, or safety. The minimal info leaves significant gaps for an agent.

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 concise (one sentence) and front-loaded with 'Perform a Splitwise action', but it lacks substance. It lists actions without explanation, which is adequate but not highly effective.

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 complexity (7 parameters, no schema documentation, no output schema, no annotations), the description is severely incomplete. It does not explain how to structure calls for different actions, what parameters are required for each, or the expected return values. The tool definition fails to provide sufficient context for an agent to use it correctly.

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 0%, but the description does not explain any parameter meaning or relationships. The actions list gives some context for the 'action' parameter but ignores all others (api_key, group_id, description, cost, currency_code, users). The description adds minimal value beyond the schema.

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 it performs Splitwise actions and lists five specific actions (get_groups, get_expenses, etc.), giving some clarity. However, it does not explain what each action does or how the tool dispatches them, making it somewhat vague for distinguishing from other tools.

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 no guidance on when to use this tool vs alternatives, no prerequisites, and no context for choosing among the listed actions. It only implies that the tool is for Splitwise operations, but explicit usage guidelines are missing.

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