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

Annotations already declare it as a safe, read-only, idempotent read, and the description adds material context beyond them: the API key from trnch_register must be sent as an Authorization Bearer header, polling should be throttled to every few seconds, and the new-holds variant carries higher risk. That is real behavioral disclosure, not restatement.

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?

Dense but front-loaded: what the feed is, what a token looks like, how to paginate, how to poll, and what auth is needed, with zero filler sentences.

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?

No output schema exists, so the description carries the return burden and does it: it enumerates the token fields (rank, Heat score, price, liquidity, volume, price changes, entry time) and the nextSince cursor. Auth and rate guidance round out everything needed to call it 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?

Schema coverage is 100% and the single `since` parameter is already documented as 'nextSince from the previous call.' The description reinforces the round-trip usage ('pass it back as since') but adds no format or edge-case detail the schema lacks, so it sits at the baseline.

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?

Opens with a specific verb+resource ('Read the live Heat') and immediately disambiguates the two sub-feeds: heat = screened/ranked tokens, new holds = just-spotted, higher risk. An agent knows exactly what comes back without opening a schema.

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?

Gives concrete operating guidance: poll at most every few seconds, pass token ids to trnch_buy or trnch_sell, pass nextSince back as since for only new entries, dedupe by id. It lacks an explicit 'when not to use this' or a comparison to another feed, but the follow-up routing to siblings is clear.

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