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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety profile is covered. The description adds genuinely new behavioral context: the deletion is permanent and already-scheduled posts originating from the template survive, which is exactly the blast-radius information an agent needs before a destructive call.

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?

Three short sentences, no filler, with the destructive action front-loaded and the consequence and user-confirmation caveat following in priority order. Every sentence 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 an irreversible single-parameter delete with no output schema, the description covers permanence, side-effect scope, and the confirmation requirement — enough to call it correctly. It stops short of stating authorization requirements or recovery options if the template is deleted in error.

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?

There is only one parameter and schema description coverage is 100%; the schema itself explains template_id is a UUID sourced from list_post_templates. The description adds no format, ID-discovery, or naming semantics beyond that, so the baseline 3 applies.

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?

Names a specific verb (delete) and resource (saved post template), with the adverb 'permanently' pinning down the operation's semantics. The resource name cleanly separates it from siblings like delete_post_tag, delete_persona, and delete_media without needing the schema.

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?

Gives one real usage instruction — 'Confirm with the user first' — which tells the agent to gate the call on user approval. However, it never names alternatives (e.g., update_post_template to modify rather than remove) or states prerequisites such as ownership or permissions.

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