Get web alt-data (trends, IV, pageviews)

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds valuable context: data is cached, keyed by source, and includes fetchedAt timestamps. The structure under `data` is also disclosed, going beyond the annotations without contradicting them.

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?

Three sentences pack a lot: the tool's purpose, the list of sources, the response structure, and the relationship to a sibling tool. No fluff, front-loaded with the key noun phrase 'Generic cached alternative-data'.

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 one-parameter cached-data tool without an output schema, the description provides enough context about what is returned (sources, structure, timestamps) and how it fits with alternatives. It could be slightly more explicit about the response shape but is largely complete.

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 has one parameter 'ticker' with no description (0% coverage), so the description carries the burden. It says 'for a ticker' which implies the purpose but does not specify format (e.g., uppercase, exchange suffix) or other constraints. Minimalistic but functional.

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 retrieves cached alternative data for a ticker, listing specific sources (google_trends, wikipedia_pageviews, options_iv, openinsider, edgar_8k). It differentiates from the sibling tool stoquant_get_alt_signals by noting it 'complements' it with raw data, which is a specific verb+resource+scope.

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 mentions complementing stoquant_get_alt_signals, which gives clear context on when to use this tool for raw alternative data vs derived signals. It lacks explicit exclusions (e.g., when not to use), but the relationship to alternatives is clearly stated.

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