ofw_get_notifications

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

The description discloses a critical side effect: 'updates your last-seen status.' This is valuable behavioral context beyond the readOnlyHint annotation, which might otherwise lead an agent to assume no state changes. The annotation says readOnlyHint=true, but the description correctly warns of a state mutation, so there is no contradiction—the description adds important nuance.

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, compact sentence that front-loads the tool's purpose and then adds the critical side-effect warning. Every word earns its place; no filler or repetition.

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 tool with no output schema, the description adequately covers what the tool does and its side effect. It could be slightly more complete by noting whether the returned summary includes counts only or also details, but the core information an agent needs is present.

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 doesn't need to explain parameter meaning. The baseline for 0 params is 4, and the description appropriately focuses on what the tool returns rather than parameters.

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 tool retrieves a dashboard summary with specific content types (unread message count, upcoming events, outstanding expenses). It distinguishes itself from siblings like ofw_list_messages or ofw_list_events by being a summary rather than a detailed list, though it doesn't explicitly name a sibling alternative.

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 implies this is the tool to use when you need an overview of multiple data types at once, rather than detailed lists. However, it doesn't explicitly state when to use this over alternatives like ofw_list_messages or ofw_list_events, nor does it mention any exclusions.

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