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

The destructiveHint annotation is consistent with the 'delete' action; no contradiction. The description does not elaborate on side effects, but annotations already convey the destructive nature.

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 text is brief, but there is slight redundancy between 'Delete paragraph.' and 'Delete one agenda event paragraph...' which could be streamlined without losing clarity.

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?

Together with the schema and annotations, the description provides enough context for an agent to call this tool correctly. No output schema is needed for a delete operation.

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 schema descriptions are detailed (event ID and paragraph ID with source references), so the added description contributes little beyond restating the paragraph ID usage. Baseline 3 applies given high schema coverage.

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 (delete) and the resource (agenda event paragraph), distinguishing it from other paragraph deletion tools via the type specification.

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?

It identifies the target by paragraph ID and mentions the event context, but does not explicitly contrast with sibling delete tools. However, the event qualifier makes the appropriate usage clear.

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