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

Annotations already declare destructiveHint=true and idempotentHint=false, so the destructive nature is covered. The description adds no context about permanence, side effects, or prerequisites. It merely restates the action without enriching behavioral understanding.

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 terse, but the structure is awkward: 'Delete paragraph. Guidance: Delete one video paragraph by paragraph id. | context: id, paragraph_id' includes a redundant 'context' section that doesn't add value. It's concise but not well-organized.

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 mutation with no output schema, the description is minimal. It doesn't mention what happens on failure, whether deletion is permanent, or any dependencies. Given the large sibling list, it also fails to differentiate when to use this tool over others, making it incomplete.

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 descriptions fully cover both parameters (id and paragraph_id) with clear provenance (from cms_list_videos and cms_list_video_paragraphs). The description's 'context: id, paragraph_id' adds nothing beyond the schema, so baseline 3 for 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 states 'Delete one video paragraph by paragraph id', which is a specific verb+resource. It distinguishes from sibling delete tools by explicitly naming 'video paragraph'. However, the first line 'Delete paragraph' is generic, though the guidance clarifies the exact target.

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?

No explicit guidance on when to use this tool versus the many sibling delete-paragraph tools (e.g., cms_delete_article_paragraph). The description only says it deletes a video paragraph, which is inferred from the name, but doesn't provide conditions or exclusions.

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