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

With no annotations, the description must disclose behavioral traits. It appropriately discloses the permanent/destructive nature of the operation. However, it lacks details on required permissions, error conditions, or side effects, which would be valuable for a mutation tool, so transparency is moderate.

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?

The description is a single, focused sentence that front-loads the key information ('Permanently delete') and uses parentheses to clarify the resource. No wasted words; it is efficiently concise.

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 simple one-parameter delete tool, the description plus schema covers the essential invocation details. It lacks information about error handling or return behavior, but given the tool's simplicity, this is a minor gap, making it adequately complete.

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?

The input schema already fully describes the single 'id' parameter as 'Presentation ID' (100% coverage). The description adds no parameter-specific meaning beyond the schema, so it stays at the baseline score of 3.

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?

The description clearly identifies the action ('Permanently delete') and the resource ('slide presentation'), with synonyms to disambiguate. It distinguishes from sibling delete tools like delete_document and delete_sheet by specifying the resource type, achieving a specific and unique purpose.

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 implies usage based on resource type but does not explicitly state when to use this tool versus alternatives. It doesn't mention exclusions or alternative tools, so the guidance is only implicit from the tool name and parenthetical.

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