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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the agent knows this is a permanent, mutating, externally visible operation. The description adds nothing behavioral beyond that — it does not state whether the deletion is reversible, whether it requires a publish step first, or what happens to related data. Given the annotations carry the safety profile, a baseline 3 is appropriate.

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?

Extremely tight: one action sentence followed by param notes. The purpose is front-loaded, and there is no filler or repetition. Every line serves a purpose.

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?

An output schema exists, so return values need not be documented, and annotations cover the destructive/safety profile. For a two-parameter destructive tool this is close to adequate, but the absence of any irreversibility or prerequisite note, plus the tautological project_id description, leaves a small completeness gap.

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. It does so well for post_id, clarifying it can be a UUID from a list response or a full SK like cms-post-data-<uuid> — genuinely useful format guidance. However, project_id is only restated tautologically ('The project ID'), leaving half the parameters without added meaning.

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: 'Delete a CMS blog post'. This distinguishes it from the many other delete_* siblings (delete_assets, delete_cms_category, delete_directory_item) by naming the exact resource. It stops short of differentiating itself from adjacent CMS post tools (unpublish_cms_post, update_cms_post), but the purpose itself is unambiguous.

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?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. With siblings like unpublish_cms_post and update_cms_post in the same CMS post family, the description should clarify that this permanently removes the post rather than merely unpublishing it, but it offers no such routing. The agent is left to infer usage entirely.

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