Corpus MCP Server

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action without clarifying read-only safety, pagination behavior, data freshness, or whether 'all' holdings includes delisted/zero-quantity positions.

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?

Description is a single, efficient four-word sentence with no redundancy. It immediately communicates the core operation without filler, appropriate for a zero-parameter tool.

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?

With zero parameters and an output schema available, the description adequately covers the basic invocation pattern but lacks context regarding how this comprehensive listing relates to sibling aggregation tools (e.g., 'get_portfolio_summary') or filtered views (e.g., 'get_top_holdings').

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?

Input schema contains zero parameters. Per scoring baseline, this dimension receives a default score of 4 as there are no parameter semantics to elaborate upon.

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?

Description clearly states the verb (List) and resource (stock holdings), establishing a clear purpose. However, it does not explicitly differentiate from sibling 'get_top_holdings' (which returns a subset) or 'get_portfolio_summary' (which aggregates across asset classes), leaving some ambiguity about when to prefer this tool over those alternatives.

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?

Description provides no guidance on when to use this tool versus siblings like 'get_top_holdings' or 'get_portfolio_summary', nor does it mention prerequisites such as authentication requirements or portfolio setup.

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