dismiss_notification

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

Annotations already declare idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context — 'grouped cards dismiss together' — warning that a single dismiss can affect multiple items. It stops short of stating reversibility or what happens with an unknown/stale id.

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?

One compact sentence, front-loaded with the action and resource, with the grouped-card caveat placed where it is most useful. No filler.

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 simple and annotations cover the safety profile, but with no output schema and zero schema coverage, the description should say where ids come from and what a dismissal returns or how failures behave. Those gaps are modest but real.

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 0%, so the description must carry the single parameter — it does identify that dismissal is keyed 'by its id', and the grouped-card note adds scope meaning. However, it gives no id format and no hint about where to obtain a valid id, leaving the one parameter only partially explained.

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?

States a specific verb ('Dismiss') and resource ('inbox notification/card') plus the key qualifier 'by its id'. It implicitly separates itself from snooze_notifications and get_recent_notifications through the verb, though it never names those siblings explicitly.

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?

Usage is only implied by the verb: an agent can infer 'dismiss reads as removing a notification', but there is no guidance on when to dismiss vs snooze_notifications, or whether the id must come from get_recent_notifications. No exclusions or prerequisites are stated.

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