equivault-mcp

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

No annotations are provided, so the description carries full burden. It mentions 'real-time' which is useful behavioral context, but doesn't disclose rate limits, authentication needs, data freshness guarantees, or what happens with invalid tickers. For a tool with zero annotation coverage, this leaves significant 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?

The description is a single, efficient sentence that front-loads the core functionality. Every word earns its place with no redundancy or unnecessary elaboration, making it optimally concise for this simple 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?

Given the tool's simplicity (1 parameter, 100% schema coverage, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It doesn't address return format, error handling, or how it differs from sibling tools, leaving the agent with gaps despite the straightforward nature.

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 single parameter 'tickers' fully documented in the schema. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of valid symbols, no mention of maximum number of tickers). Baseline 3 is appropriate when schema does the heavy lifting.

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 verb 'Get' and resource 'real-time stock quotes' with scope 'for one or more ticker symbols', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_company' or 'get_financials' which might provide overlapping financial data, so it doesn't reach the highest tier of sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools available (e.g., 'get_company', 'get_financials', 'get_metrics'), there's no indication whether this is for price-only data or broader financial information, nor any prerequisites or exclusions mentioned.

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