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

With no annotations provided, the description carries the burden of behavioral disclosure. It conveys a read-like lookup, a 'current' snapshot, score bounds, and a single-ticker scope. It does not mention error cases or freshness limits, but for this simple operation the disclosure is reasonably adequate.

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 one dense, high-value sentence that front-loads the output and instantly explains the main use case. There is no filler or repetition.

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 a single parameter, no output schema, and no annotations, the description still explains the return fields well: score, signal label, confidence, one-line reason, and range. An agent can understand what the tool offers and call it with just the symbol.

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 the only parameter completely, including type, required status, and examples like NVDA or BRK.B. The description only reinforces the existing 'US ticker' constraint and adds little beyond what the schema already provides.

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 states a clear action (get), a specific resource (a single US ticker's Tapeline score), and exactly what is returned: six-factor score, confidence, and reason. This is distinct from sibling tools like get_ticker_record or search_tickers.

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?

It explicitly says to use this tool when asked what Tapeline says about a specific stock, so the primary trigger is clear. It does not name alternative tools or exclusion cases, but the guidance is sufficient for this simple lookup.

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