pinecone_delete_records

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

With no annotations, the description carries the full burden. It discloses the important confirm-required guard for delete_all, which is real behavioral value, but omits that deletion is irreversible, whether ids/filter/delete_all are mutually exclusive, and any permission requirements.

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, front-loaded with the resource and modes, with the confirm constraint in its own paragraph. Nothing is wasted, though the extreme brevity leaves gaps for a 6-parameter destructive tool.

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. For a destructive, unannotated, 6-parameter tool at 0% schema coverage, however, the description should say more about irreversibility and parameter mutual exclusivity than it does.

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% across 6 parameters, so the description must compensate. It explains what ids, filter, and delete_all mean and clarifies the confirm coupling, but leaves index unexplained and does not state whether the id/filter/delete_all paths are alternatives.

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 (delete) and resource (records) and enumerates the three deletion modes (by id, by metadata filter, clear namespace). It implicitly differentiates from pinecone_delete_namespace and pinecone_purge_expired, but does not name the boundary explicitly, so it stops short of the top score.

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 when each mode applies by listing them, and adds the guard that delete_all requires confirm=true. It gives no guidance on choosing between ids vs filter vs delete_all, nor when to reach for a sibling such as delete_namespace instead.

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