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

Goes well beyond the annotations: it discloses the access model (7-day free trial subscription, x402 pay-per-call wallet) and the failure mode (returns a PaymentRequired object with no data without one), plus the self-described `schema` block and awareness block structure. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the resource and payload contents, followed by field structure and then the payment/access caveats. Dense but every clause carries information; minor redundancy in restating payload contents twice.

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?

With no output schema, the description takes on the burden of explaining returns, and it does so (coil fields, awareness block, self-describing schema block) while also covering the payment-required failure path. An agent has enough to invoke and interpret it.

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 tool takes no parameters, so the baseline is 4. The description correctly implies a no-argument, single-shot read rather than inventing parameter semantics that do not exist.

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 specific verb+resource ('complete live board in one payload') and enumerates exactly what it contains (scored names, sector lanes, buy-list lanes, regime/crypto books). This implicitly distinguishes it from the granular siblings (get_buy_list, get_crypto_day, get_market_regime), though it never names an alternative outright.

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?

Usage is implied by 'complete ... in one payload' and 'Live intraday version', which hints at when to use this aggregate vs. the per-slice siblings and vs. the as-of variant. However, no explicit when-to-use or when-not-to-use statement, and no sibling is named.

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