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

No annotations are provided, so the description carries the burden. It implies a read-only snapshot by describing 'Current' data and likening it to a GET endpoint, and it discloses the returned fields, which is useful. It does not state freshness guarantees (beyond updated_at), rate limits, or whether the listing is paginated, which are the remaining behavioral gaps.

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?

Two tight sentences with zero filler. The resource and its contents are front-loaded before the secondary REST-equivalence note, so an agent gets the essential information immediately.

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 parameters, no annotations, and no output schema, the description must describe the payload itself, and it does so by naming the exact fields returned. That covers the main need for a zero-arg read tool. Minor gaps remain around data freshness and whether the result is bounded (top-N vs all assets is stated, so this is largely covered).

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 there are no parameter semantics to explain; a baseline of 4 applies. The description correctly reads as a parameterless snapshot endpoint rather than implying hidden arguments.

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?

States a specific resource (the 'Current Tickerz Heat board') and enumerates exactly what it returns: all tracked assets with price, 24h move, Heat (0-100) and updated_at. An agent knows precisely what this tool yields. It does not, however, explicitly differentiate itself from siblings like asset or methodology, so it stops short of a 5.

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?

There is no statement of when to reach for this tool versus the sibling set (asset, methodology, receipts). The 'Same data as GET /api/board' note is a REST-equivalence fact, not usage guidance or an exclusion. The agent must infer usage from the description alone.

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