sw_get_notifications

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

The readOnlyHint annotation already covers the safety profile, and the description adds only the qualifier 'recent' without specifying the exact time window or response format. Since there is no output schema and the description does not disclose pagination or limits, it provides minimal additional behavioral context 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, concise sentence that immediately states the action and resource without any redundant words. It earns its place fully.

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 no parameters and no output schema, the description is adequate but leaves gaps: 'recent' is ambiguous, and it does not describe the return structure or any limits. More detail about what constitutes 'recent' or the notification payload would improve completeness.

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 input schema is empty, and the baseline for 0 parameters is 4. The description correctly does not need to explain parameters, and there is no missing information to compensate for.

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 uses the specific verb 'Get' clearly identifying the resource as 'recent Splitwise activity notifications' and scoping it to 'the current user'. This distinguishes it from all sibling tools, none of which mention notifications.

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 that this retrieves notifications for the current user, which is distinct from the other tools. However, it does not explicitly state when to use this versus alternatives or exclude specific scenarios, but the uniqueness of 'notifications' implies appropriate usage.

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