mdl_notifications_clear_all

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds a genuinely new fact (host-configured MyDramaList authentication is required), but 'Changes data on MyDramaList' largely restates destructiveHint, and it does not say the clear is irreversible or scoped to the whole account.

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?

Three short clauses, front-loaded with the action, followed by the prerequisite and the caution. No filler, though the 'Notifications:' label-prefix style is slightly mechanical rather than flowing prose.

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?

With zero parameters, no output schema, and annotations already carrying the destructive/idempotency profile, the description covers the remaining agent-relevant facts (auth prerequisite, explicit-request gating). Only irreversibility and the single-vs-all distinction are left unstated.

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 takes zero parameters, so there is nothing for the description to clarify. Baseline 4 applies; no parameter-level information is missing.

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 and resource with an explicit scope: 'clear all' notifications. The 'all' scope implicitly separates it from the sibling mdl_notifications_clear, but the description never names that sibling, so differentiation is left to inference.

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?

Gives a clear usage condition for a destructive operation: 'use only for an explicit user request,' which tells the agent not to fire it autonomously. It stops short of naming the narrower alternative (mdl_notifications_clear) for clearing a single notification.

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