Delete a post template owned by the caller (or an internal template in the caller's organization, if the caller is an org admin/owner).

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds beyond that: an explicit confirmation requirement and the important note that provider errors count as failures even when HTTP 200 is returned. It does not describe revertibility or the success response shape, but the added context is solid.

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?

Purpose is front-loaded, which is good, but the text contains a double-period typo ('...owner)..') and the 'Current Buffer GraphQL deletePostTemplate' fragment is an implementation aside that interrupts the flow. Sentence ordering is serviceable but not tight.

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 and six fully documented parameters, the description covers confirmation, authorization scope, and provider error semantics. It omits what a successful return looks like and any undo/recovery note, but on the whole an agent has enough to call it correctly.

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 100%, so the schema already documents all six parameters thoroughly, setting the baseline at 3. The description does map loosely onto two params (the confirm flag and the fields/upstream-field bounding), but it adds no syntax or semantics beyond what the schema already states.

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 and resource (delete a post template) and adds a meaningful ownership scope: caller-owned templates, or internal org templates for admins/owners. This clearly separates it from siblings like get_post_template, update_post_template, and create_post_template. It largely restates the title rather than adding new distinguishing detail, so it stops short of a 5.

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 gives a real usage prerequisite ('Requires explicit confirmation') and an authorization condition (org admin/owner scope), which are useful before an agent calls it. However, it never states when NOT to use it, nor names an alternative for retrieving or editing templates. Guidance is implied rather than exhaustive.

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