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

The annotations already declare readOnlyHint and openWorldHint, so the description is not required to restate that the tool is safe and read-only. The description adds the contents of the view but no operational traits such as data freshness, pagination, or error behavior. It does not contradict the annotations.

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 compact sentence with the main idea front-loaded ('Full per-ticker research view') followed by a precise colon-separated list of contents. There is no filler, repetition, or unnecessary context.

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 read-only tool with an output schema and safety annotations, the description covers the main content. The main gap is contextual routing: with 16 sibling tools, the description does not say how this aggregate view compares to more targeted ticker tools, leaving selection partly to inference.

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 0%, so the description must compensate for the one required parameter. 'Per-ticker' partially indicates that symbol is a ticker symbol, but that mostly restates the tool name and does not specify expected format, casing, or examples. The description provides only minimal added meaning beyond the schema's bare 'Symbol' field.

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 identifies a specific resource—the per-ticker research view—and lists its contents: score, lane membership, per-source signals, virality, consensus, cluster-rotation position, and forward returns. This makes it recognizable as an aggregate research snapshot and distinguishable from ticker-price, ticker-articles, and ticker-analyst siblings. It does not explicitly name those siblings, so it misses the top score by a small margin.

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 phrase 'Full per-ticker research view' gives a clear implied usage: use this tool when you need comprehensive research data for one symbol. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of the many sibling ticker-scoped tools that might be more appropriate for narrower questions.

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