layout_asset_delete

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

Description adds 'IRREVERSIBLE' and the behavior of templates rendering with empty content, going beyond the destructiveHint annotation to explain exact impact.

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 concise sentences with no fluff. Each sentence adds essential information: action, irreversibility, usage condition, and consequence.

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 delete tool, the description covers all critical aspects: what it does, irreversible nature, parameter requirement, and downstream effect. No output schema needed.

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?

Only the 'force' parameter is explained; 'site' and 'asset_id' are not described. With 0% schema coverage, the description fails to add meaning for two required parameters.

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?

Clearly states 'Delete a layout_asset' with emphasis on irreversibility. Distinguishes from layout_asset_create and layout_asset_update.

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?

Explicitly states that the tool 'Refuses without force=true', providing a clear usage condition. Mentions consequence (templates render empty), but no guidance on when not to use.

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