MCP Stock Market

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

With no annotations provided, the description carries full burden but only states it uses Alpha Vantage API without detailing rate limits, authentication needs, data freshness, or return format. It mentions 'recent' but doesn't define timeframe, leaving behavioral gaps.

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?

Single sentence, front-loaded with core purpose, zero waste. Efficiently conveys key information without unnecessary details, making it easy to parse.

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 simple 1-parameter tool with no output schema and no annotations, the description is minimally adequate but lacks details on return values, error handling, or API constraints. It covers the basic purpose but leaves contextual gaps for effective use.

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 100%, with the parameter 'symbol' fully documented in the schema. The description adds no additional parameter semantics beyond implying ticker symbols like AAPL or MSFT, which is already covered, so baseline 3 applies.

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 states the action ('Get') and resource ('dividend payout history for a ticker symbol'), specifying the data source (Alpha Vantage API). It distinguishes from siblings like getStockPrice or getCompanyOverview by focusing on dividends, but doesn't explicitly contrast them.

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 on when to use this tool versus alternatives like getCompanyOverview (which might include dividend info) or other financial data tools. The description implies usage for dividend history but lacks explicit context or exclusions.

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