pinecone_delete_index

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

With no annotations, the description carries the full burden and does disclose the two most important traits: the operation is destructive and cascades to all contained data, and it is gated behind an explicit confirm flag. It stops short of saying the deletion is irreversible or what permissions are needed.

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?

Two short sentences, zero filler, with the destruction scope stated first and the safety prerequisite second. Nothing could be removed without losing meaning.

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?

An output schema exists, so return values need not be explained, and the description covers scope and the confirm gate. For a destructive, non-annotated tool it would ideally also note irreversibility or permission requirements, but the essentials for correct invocation are present.

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 0%, so the description must compensate; it does for the critical parameter by stating confirm=true is required (the schema only shows a boolean defaulting to false, which is misleading on its own). The 'index' parameter receives no elaboration, but its meaning is self-evident from the name.

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 an index') plus the cascading scope ('and everything in it'), which distinguishes it from sibling deletions like pinecone_delete_namespace or pinecone_delete_records. It does not, however, explicitly name an alternative or state when this deletion is preferred over those siblings.

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 one concrete precondition ('Requires confirm=true'), which is genuine usage guidance for the highest-risk parameter. It offers no guidance on when to choose this tool versus the other deletion tools (namespace, records, purge_expired) or what state must exist beforehand.

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