vectordb_optimize_search

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only adds that this is a 'Pro feature' and says 'Optimize', but does not explain whether it modifies the vector index, changes search parameters, requires special permissions, or has side effects. This is minimal behavioral context with significant gaps.

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 one short, focused sentence with no filler. The main action and resource are front-loaded, and the parenthetical 'Pro feature' adds a useful availability signal without bloating the definition.

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?

For a tool with no annotations, no output schema, and only 50% parameter documentation, the description is too thin. It does not say what 'optimizing' actually changes, when it should be called, what prerequisites exist beyond 'Pro', or how api_key/directory are used. An agent could invoke it but with low confidence about its effect.

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?

The schema documents only 'directory' as 'Project directory', leaving api_key without a schema description. The tool description does not explain the api_key's role or how it relates to the 'Pro feature', and it adds no parameter-level meaning beyond what the schema already provides.

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 names a specific verb ('Optimize') and resource ('vector search performance'), so an agent can tell this is about tuning an existing vector search setup rather than setting one up. It is clear, though it does not explicitly contrast with the many sibling 'optimize' tools or vectordb_setup/vectordb_generate_index.

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 is given on when to use this tool versus alternatives such as vectordb_setup, vectordb_generate_index, or searchidx_optimize. The description implies 'use this to optimize vector search performance,' but that is just a restatement of the tool's purpose, not a usage guideline.

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