hyperspace_search_wasserstein

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

With no annotations, the description still discloses the return shape (JSON array of top_k matches with id, score, payload) and the ranking basis (Wasserstein distance), which is real value. It omits permission/auth requirements, cost/performance profile, and whether top_k is capped or results can be empty.

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 tight sentences, front-loaded with the distinguishing method, then the return contract. No filler or repetition of the tool name.

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 3-parameter read tool with no output schema, the description does explain what comes back and how it is ranked, which is the key gap. It still leaves the agent without guidance on choosing this over sibling search tools or on limits/performance, so it is adequate but not complete.

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%, so the description must compensate: it does assign roles to all three parameters (text searched, collection scope, top_k result count). However it gives no format or constraint detail (e.g., top_k bounds, collection naming, how text is embedded/compared), so the gap is only partially filled.

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?

Names a specific verb (search) plus a distinct method (Optimal Transport / Wasserstein) and the resources it operates on (collection, text). This clearly distinguishes it from the plain-text sibling hyperspace_search_text, though it never names that sibling explicitly.

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 phrase 'Compares distributions/complex concept overlap' implies when this is appropriate (fuzzy distributional similarity rather than lexical match), but there is no explicit when-to-use/when-not guidance and no named alternative such as search_text or explore_graph to route between.

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