Dismiss notification

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is largely covered by structured data. The description adds only the HTTP endpoint, and says nothing about the confirm flag the schema exposes, whether the notification is permanently removed, or what happens on an unknown 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?

Two short lines, front-loaded with the action statement. The endpoint line is compact and moderately useful, though it occupies roughly half the description with implementation detail rather than agent-facing guidance.

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?

This is a destructive operation with a confirmation parameter, and the description never explains when the confirm flag is needed or what the confirmation flow is, leaving that entirely to the schema's own field text. For a mutation tool with no output schema, the definition is thinner than the operation warrants.

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 50%: the confirm parameter is documented in the schema, while notification_id has no description. The endpoint template implicitly clarifies that notification_id identifies the target notification, but adds no format, sourcing, or error semantics 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?

"Dismiss one notification" gives a specific verb (dismiss) and a scoped resource (one notification), which is clearly narrower than the sibling nextcloud_list_notifications. The raw DELETE endpoint reinforces that this removes a single notification identified by ID. It stops short of 5 because it never explicitly contrasts itself with the listing sibling or states what dismissal means for the notification.

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?

There is no when-to-use guidance, no prerequisite (e.g. needing the notification ID from nextcloud_list_notifications), and no mention of alternatives or when not to call it. The only implicit guidance is the path template, which merely restates the required parameter.

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