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

With no annotations, the description carries the full disclosure burden and does more than just say 'read'. It reveals that the result is a single live payload, that fields are self-describing and may appear upstream before docs update, and that each call costs $0.25 USDC. It does not mention auth or rate limits, but the essential behavioral traits are covered.

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 dense but each sentence earns its place: scope, component list, per-name fields, dynamic schema behavior, and pricing. The key purpose is front-loaded, and no filler or structural repetition exists.

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 no-input tool with no output schema, this is nearly complete: it names all payload sections, describes embedded self-describing metadata, and states the cost. It is only lightly limited by not mentioning potential failures, latency, or payment mechanics, but those are reasonably inferable.

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?

There are zero parameters and schema coverage is 100% by default, so there is nothing to clarify about arguments. The description focuses on the payload shape instead, and the mention of a self-describing schema block is useful.

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?

Starts with 'The complete LIVE board in one payload', naming the exact resource and scope—every scored name across S&P 500, Nasdaq-100, and macro, plus sector, buy-list, regime, and crypto books. This clearly differentiates it from sibling single-read tools like get_stock_read_live or get_sector_read_live, and 'flagship read' reinforces its unique role.

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 context that this is the all-encompassing board read and says there is 'no free counterpart', implying it is the go-to for a complete snapshot. However, it never explicitly states when to choose it over the sibling tools or when not to use it, leaving the agent to infer the boundary.

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