archive_all_notifications

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds that the tool returns a count. However, it does not disclose the scope (e.g., user's notifications vs system-wide) or mention any side effects beyond archiving. The behavior is partially transparent but lacks full context.

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 extremely concise—two sentences that convey the action and return value without any unnecessary words. It is front-loaded and efficiently communicates the core purpose.

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?

Given the presence of an output schema, the description adequately states it returns a count. However, it lacks clarity on the scope of notifications being archived (user-specific or global) and does not address potential prerequisites or limitations. It is minimally complete but leaves room for ambiguity.

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, and the input schema is fully covered (100%). The description does not need to explain parameters. The baseline for zero parameters is 4, and no additional information is required.

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 action ('Archive all notifications') and the resource ('notifications'), with a specific verb. It distinguishes from siblings like 'archive_notification' (singular) by indicating bulk operation. The return value (count) is also mentioned.

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 a bulk archiving operation but provides no explicit guidance on when to use this tool versus alternatives like 'archive_notification' or 'archive_notification_context'. The context from the name and sibling list suggests it's for batch archiving, but no when-to-use or when-not-to-use criteria are given.

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