delete_daily_forum_message

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

With no annotations provided, the description carries the full disclosure burden, and it does the most important part: revealing that the default (confirm absent/false) is a non-destructive preview, so the agent knows deletion only occurs when confirm=true is passed. It stops short of saying the deletion is irreversible or what errors/authorization are involved, which leaves some behavioral gaps for a mutation tool.

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, front-loaded sentences with zero filler: the action first, then the safety-relevant condition. Every word earns its place.

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?

For a destructive, no-annotation, no-output-schema tool, the description covers the preview/confirm gate but omits irreversibility, failure modes, and authorization. An agent could invoke it correctly given the confirm semantics, but the risk profile is only partially described.

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 description coverage is 0%, so the description must compensate for both parameters. It does explain the semantics of 'confirm' (gate for actual deletion vs preview), which is the non-obvious one, but says nothing about 'message_id' (e.g. format, source, what happens if the ID does not exist).

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+resource ('Supprime un message du forum du jour'), which cleanly separates it from the sibling post_daily_forum_message and update_daily_forum_message. It does not, however, explicitly name a sibling or explain how it differs from those at the behavioral level.

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 clause 'Sans confirm=true : aperçu seulement' tells the agent the exact two-step pattern (preview first, then confirm) for this specific tool. Beyond that there is no when-to-use guidance, no mention of alternatives such as update_daily_forum_message, and no prerequisites such as required permissions.

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