equivault-mcp

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. It effectively describes the tool's scope (multiple research components) and access constraints (tier-based availability), but lacks details on rate limits, authentication needs, response format, or whether it's read-only (implied by 'Get' but not explicit).

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 front-loaded with the core purpose, followed by specific components and access notes in a single, efficient sentence. Every phrase adds value without redundancy, making it appropriately sized and well-structured for quick comprehension.

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 moderate complexity (aggregating multiple data sources) and no annotations or output schema, the description does well by outlining components and access constraints. However, it could improve by hinting at the return structure or error handling, leaving some gaps for a tool with no output schema.

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?

The schema description coverage is 100% for the single parameter, so the baseline is 3. The description adds value by explaining the optional portfolio_id's effect ('portfolio analytics are included'), enhancing understanding beyond the schema's basic documentation, though it doesn't provide format examples or deeper semantics.

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 tool's purpose with specific verbs ('Get a daily research summary') and resources ('signal dashboard, trending signals, recent briefs for followed companies, portfolio analytics'), distinguishing it from siblings like get_signal_dashboard or get_trending_signals by bundling multiple components into one comprehensive briefing.

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 clear context for usage ('daily research summary') and mentions tier-based access restrictions, but does not explicitly state when to use this tool versus alternatives like get_signal_dashboard or get_trending_signals individually, nor does it outline exclusions or prerequisites beyond tier limitations.

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