deleteEmbeddingIndex

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known; the description adds real value beyond that by disclosing irreversibility and the collateral effect of removing all stored embedding vectors, plus a confirmation requirement. It does not cover permissions, rate limits, or failure modes, keeping it below a 5.

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?

Four short sentences, zero filler, with the destructive action and its scope front-loaded before the prerequisite and confirmation guidance.

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 no explanation; the description covers the destructive consequence, irreversibility, confirmation requirement, and ID acquisition path. Minor omissions such as required permissions or post-delete side effects on related indexes keep it from being fully exhaustive.

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% for the single indexId parameter, so the schema already carries the parameter documentation; the description's 'by its ID' and the findEmbeddingIndexes hint add modest routing value but no format or type detail beyond the schema.

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 plus resource ('Delete an embedding index policy by its ID') and adds the secondary effect of stripping stored embedding vectors, which distinguishes it from sibling tools like deleteTextIndex and deleteRecord. An agent can identify the target and scope without opening the schema.

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?

Gives a clear prerequisite path ('Use findEmbeddingIndexes to get the indexId') and a mandatory safety step ('Confirm with the user before calling'). It does not state when this tool is not appropriate or name a delete alternative, but the context and gating condition are unambiguous.

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