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

The destructive nature is already indicated by the destructiveHint annotation, and the description simply says 'Delete video item' without adding extra behavioral context such as irreversibility or cascading effects. It does not contradict the annotations.

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 and front-loaded. It immediately states the action and the key parameter, with no unnecessary elaboration or filler.

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 simple delete operation with one documented parameter and a destructive annotation, the description is largely complete. It does not explain return values or side effects, but these are not essential given the tool's simplicity and existing annotations.

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 already provides full coverage for the single id parameter, including its type, minimum, and provenance. The description only repeats the parameter usage without adding meaningful semantic detail beyond the schema.

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: deleting a single CMS video item by its ID. The resource and verb are unambiguous, and it is distinct from sibling tools like cms_delete_video_paragraph.

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 usage when a video item needs to be deleted, but it does not explicitly compare with alternatives or state when not to use this tool. The intended context is mostly inferred from the title and resource type.

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