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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the destructive nature is covered structurally. The description adds one piece of behavioral context not in the annotations — 'Auth required' — but says nothing about irreversibility, cascade effects on bookings or automations using the template, or error behavior for an unknown id.

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?

One sentence, front-loaded with the verb and resource, with the scope constraint and auth note appended. Nothing extraneous.

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 one-parameter destructive tool whose safety profile is already in annotations, the minimum is met. However, a delete operation should tell the agent whether the removal is permanent and whether anything referencing the template breaks — neither is addressed.

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 coverage is 100% and the single parameter already documents the 'lt_' prefix, so the description only restates it. Baseline 3 applies: the schema does the work and the description adds no new parameter 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 and resource ('Delete a saved load template') plus the identifier used to target it, so the agent knows exactly what the tool does. Sibling names like load_templates and save_load_template make the intent easy to separate, though the description doesn't explicitly name the counterpart it inverts.

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?

'Auth required' is a prerequisite rather than usage guidance. There is no statement of when to delete versus reuse/overwrite a template, no mention of confirming with the user, and no reference to list_load_templates as the way to obtain a valid id.

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