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

With no annotations, the description fully carries the transparency burden. It details each signal's source (e.g., SEC Form 4, GitHub stars), derivation (e.g., hiring posture from department mix), and timeframes (e.g., last 90 days). It also notes the predictive nature ('precede price moves') and payment method.

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 and then enumerates signal details in a numbered list. While lengthy, each sentence provides necessary context. Could be slightly more concise but well-structured for the complexity.

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?

The description explains inputs and signals thoroughly but omits output format or structure. Given no output schema, the agent lacks guidance on what the response contains (e.g., is it a single score, individual signals, or a report?). This gap reduces completeness.

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 covers all 9 parameters with descriptions. The description adds context by grouping them into signals (e.g., 'hiring posture across Greenhouse + Lever + Ashby') and explaining usage (e.g., 'Hacker News search term'). This adds value beyond the schema but not extremely detailed.

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 multi-signal alt-data intel for investment research, listing six distinct signals. It distinguishes from sibling tools by offering a composite of hiring, insider, GitHub, Wikipedia, App Store, and Hacker News signals in one call.

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 advises to 'Pass whichever identifiers you have,' implying flexibility and partial usage. It mentions payment via x402, hinting at cost awareness, but does not explicitly contrast with single-signal tools or state when not to use.

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