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

No annotations are provided, so the description carries the full load. It discloses caching (30-minute cache) and rate limits (20 free/day), but does not state whether the tool is read-only, requires authentication, or has side effects. The 'deep' depth option implies fresh data, but permissions or idempotency are not addressed.

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 relatively concise with three sentences that cover core purpose, data sources, return items, and usage limits. The list of return items is helpful but slightly verbose. The structure is front-loaded with key information, making it easy to scan. It could be trimmed slightly without losing meaning, but overall efficient.

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 no output schema, the description adequately explains return values by listing expected components (headline signal, trending items, etc.) and notes caching and free usage. For a snapshot tool with three optional parameters, this provides sufficient context for an agent to understand what to expect. However, it could elaborate on the structure of individual return items (e.g., momentum rating format).

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 covers all parameters with descriptions (100% coverage). The description adds value by explaining the 'depth' parameter's behavior: 'snapshot' uses cache, 'deep' is always fresh. This goes beyond the enum names. For 'focus' and 'domains', the schema already provides sufficient context, so the description's extra contribution is marginal but beneficial.

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 it provides a 'real-time market intelligence snapshot' aggregated from multiple sources, listing specific data origins. The verb 'aggregates' and mention of returns indicate its function. However, it does not explicitly distinguish this tool from sibling tools that may offer similar data (e.g., substrate_breakthroughs, credithunt), missing an opportunity for 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 implies usage for a broad market overview ('snapshot') and mentions caching and free limits, but does not specify when to use this tool versus alternatives or when not to use it. With many sibling tools, explicit guidance on selection criteria would improve usability.

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