pinecone_query_vectors

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes the fact that results are ranked nearest neighbors, but says nothing about result shape (ids/scores/matches), how top_k affects response size, or whether namespace/filter change what is searched — all beyond what annotations state.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of omitting operational context entirely.

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?

With 8 parameters, no output schema, and required credentials, an agent would benefit from knowing what a query returns (matches with ids, scores, metadata/values toggled by include_* flags). The rich schema compensates somewhat, but the description leaves the response contract unstated.

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%, so every one of the 8 parameters (top_k default, filter object, vector dimension hint, index_host source) is already documented in structured form. The description adds no parameter-level meaning beyond 'nearest-neighbor', which is the baseline-3 case.

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 (Query) plus resource (Pinecone index) and the retrieval semantics (nearest-neighbor vectors), so an agent knows this is a similarity search, not a metadata scan. It doesn't explicitly name how it differs from pinecone_upsert_vectors or pinecone_describe_index, but the read/query intent is unambiguous.

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?

There is no guidance on when to choose this over the sibling Pinecone tools, no mention that index_host must come from pinecone_describe_index, and no note on when to use filter vs namespace narrowing. The agent must infer all routing from the tool name alone.

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