Corpus MCP Server

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

No annotations are provided, and the description adds no behavioral context regarding data freshness, caching, rate limits, or what the 'limit' parameter controls (days vs records).

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 extremely brief (four words), the description is not verbose; however, the single sentence fails to earn its place by providing minimal value beyond the function name itself.

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?

Though an output schema exists (reducing the need to describe return values), the complete absence of input parameter documentation and lack of behavioral context make this inadequate for a data retrieval tool.

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?

With 0% schema description coverage for the 'limit' parameter, the description completely fails to compensate by explaining what the limit restricts (e.g., number of historical records returned).

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 'Get history of gold price' is essentially a tautology of the function name and fails to distinguish from sibling tool 'live_gold_price' or clarify the temporal scope of 'history' (daily, hourly, 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?

Provides no guidance on when to use this versus 'live_gold_price' or 'get_portfolio_history', nor does it mention prerequisites like date range selection or data availability.

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