vs_query_index

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

Annotations already declare readOnlyHint=true, so the description adds minimal behavioral context beyond the HTTP method. It does not contradict annotations, but it fails to disclose additional traits like error behavior or performance characteristics.

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 concise but trivial, essentially restating the tool name. It could provide more value in the same space, such as parameter hints or usage notes.

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?

Given the tool has 10 parameters and a complex query capability, the description is too minimal. It does not explain how parameters relate, what output to expect (though output schema exists), or provide examples, making it incomplete.

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 only 20% (one parameter has a description). The description adds no parameter information, leaving most parameters (9 of 10) inadequately explained despite the low coverage requiring compensation.

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 states 'Query a Vector Search index', specifying the action (query) and the resource (Vector Search index). It distinguishes from sibling tools like vs_indexes_get (get metadata) and vs_indexes_list (list indexes) by focusing on search queries.

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?

No guidance on when to use this tool versus alternatives like vs_indexes_get or vs_indexes_sync. The description does not provide context for usage, leaving the agent without differentiation.

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