massive_search_endpoints

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds the search algorithm (BM25) and domain scope, but does not disclose additional traits like rate limits, pagination, or error conditions.

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 a single concise sentence that front-loads the core action and usage context. However, it could briefly mention the scope parameter without being verbose.

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 3-parameter schema and annotations, the description adequately frames the tool as a search/discovery tool for market data endpoints. It is complete enough for an agent to understand its role among many siblings, though parameter details and result format are missing.

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 67% (query and scope have descriptions, top_k does not). The tool description does not provide additional parameter details beyond the schema; it only hints at query content via examples. This adds minimal semantic value.

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 specifies the tool's purpose: BM25 search over all Massive market data API endpoints. It distinguishes itself from siblings by being the first step to find the right endpoint for various asset types (stocks, options, etc.).

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 advises using this tool first ('Use this FIRST'), implying it is the initial discovery tool before using more specific endpoints. However, it does not explicitly mention when not to use it or contrast with other search tools like search_prediction_markets.

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