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

With no annotations present, the description carries the behavioral burden. It usefully discloses that the data is live, refreshed every 1 second, and that the tool is not a signed order, implying read-only data access without order side effects. It does not mention pagination, rate limits, or authentication, but the core behavioral traits are clearly surfaced.

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 short and front-loaded with the main purpose, and each sentence contributes distinct information. Some phrasing is cryptic, such as 'Plug a table on /data anytime' and 'Not a signed order,' which slightly reduces clarity but does not make the description bloated.

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 three-parameter, read-only data tool, the description provides the essential context: source, freshness, snapshot/slice mode, and a side-effect caveat. However, without an output schema it does not fully define the response shape, and the effect of `limit` and `window` on the returned data is left implicit.

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 phrase 'Board snapshot ... or a slice' adds meaning to the `slice` parameter, and listing board fields helps an agent understand the returned shape. However, schema description coverage is 0%, and `limit` and `window` are not explained beyond their names and enum values, so the description only partially compensates for the missing parameter documentation.

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 identifies the tool as a fast datasource for live robinhoodtrenches.com trades, with 1-second freshness and board-snapshot or slice retrieval. It distinguishes itself from an order tool with 'Not a signed order,' but it lacks an explicit action verb like 'get' or 'fetch' and does not clearly separate itself from the many sibling talon_* analysis tools.

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 gives clear context for when to use the tool: as a datasource for a UI or an agent, and for plugging into a table on /data anytime. It also provides an exclusion ('Not a signed order'), though it does not name alternative sibling tools or describe when one of those should be preferred.

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