dismissUpdateNotice

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

Without annotations, the description carries the burden of behavioral disclosure. It explains the effect of the call (stops mentioning the specified version) and notes it will still mention newer versions. This is sufficient for a simple dismissal action, though it doesn't detail side effects or return values.

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?

Two concise sentences, front-loaded with the action and context. Every sentence earns its place, with no fluff 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?

The tool is extremely simple: one parameter, no output schema. The description fully explains when to use it, what it does, and the expected outcome. There's no meaningful gap in context for an agent to invoke 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 coverage is 100%, so the baseline is 3. The tool description reinforces that the version must be the same as the one from the _updateNotice, but the schema already provides the full description of the parameter. No significant additional semantic detail is added.

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's purpose: dismiss an update notice by passing the same version string from a previous _updateNotice. It is specific and distinguishes itself from sibling tools (syncPayslips, query, etc.) which are unrelated to update notices.

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?

It explicitly says when to call it: after the user declines an update offered via an _updateNotice field. It also explains the result (stops mentioning that version) and sets expectations about future notifications, but doesn't explicitly discuss when not to use it or alternatives.

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