Corpus MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify the time range of history, data sources, rate limits, or whether the tool returns symbol matches versus actual price data. It does not mention the output schema format.

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?

While the single sentence is concise and front-loaded, it is under-specified rather than efficiently informative. The brevity constitutes an omission of necessary context given the undocumented parameter and unclear scope.

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 undocumented parameter, lack of annotations, and likely mismatch between the tool name (suggesting symbol search) and description (suggesting price history), the description is inadequate. While an output schema exists, the input requirements and actual tool purpose remain opaque.

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 has 0% description coverage for the 'query' parameter. The description adds no clarification about what constitutes a valid query (company name, ticker symbol, partial match, regex, etc.), leaving the single required parameter completely undocumented despite the low schema coverage.

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 states a vague action ('Get history') but contradicts the tool name 'search_stock_symbol', which implies a ticker symbol lookup function rather than price history retrieval. It distinguishes from sibling 'history_of_gold_price' by specifying 'stock', but creates confusion about the actual operation performed.

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 provided on when to use this tool versus alternatives like 'get_portfolio_history' or 'history_of_gold_price', nor any indication of what input the 'query' parameter expects or prerequisites for use.

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