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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the payload contents (market cap, AI exposure, 1d/7d moves), which is useful context, but no ordering, freshness, or rate-limit information beyond that.

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?

A single front-loaded sentence that leads with the resource and packs the returned dimensions into a compact parenthetical list with no filler.

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 input schema and no output schema, the description carries the burden of describing returns, and it does so adequately by naming the metrics surfaced. Minor gaps remain (units, layer ordering, refresh cadence), but an agent has enough to decide and invoke correctly.

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 zero parameters, so the baseline of 4 applies; the description does not need to document input semantics and reasonably instead describes the output fields.

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 names the resource (buildout layers) and enumerates the exact fields returned: stock count, total and AI-exposed market cap, 1-day and 7-day moves. It does not explicitly distinguish this enumeration from the sibling get_layer (single layer) or get_buildout, so an agent must infer the list-vs-detail split from the name.

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 only implied by the 'list' verb and the plural resource; there is no explicit statement of when to call this versus get_layer or get_buildout, and no prerequisites or exclusions are given.

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