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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds real value beyond them: the UTC-day scoping of 'today', the fact that the response is conditional on whether the caller manages the product, and the extra boost-progress section that only appears for managers.

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 sentences, front-loaded with the core capability and then the conditional manager-only addition. Dense but every clause conveys content; only the parenthetical '(UTC day)' is a clarifying gloss rather than new information.

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 an output schema present the description need not document return values, yet it still summarizes the key fields, and it flags the conditional manager branch that an agent should expect. Combined with full parameter coverage and clear annotations, nothing essential is missing; only explicit alternative-routing is absent.

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 is a single 'slug' parameter with 100% schema description coverage, so the schema already carries its meaning. The description adds nothing about slug format or resolution (e.g. whether it is the product slug vs. launch slug), so the baseline 3 applies.

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 a specific verb+resource (fetch a live product's standing on today's FastDrop board) and enumerates the concrete payload: rank, qualifying votes today, the next launch above, votes needed to pass, hours left. That is far more specific than the title and clearly separates it from get_product or list_launches, though no sibling is named explicitly.

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 the phrase 'live product ... today's board', which tells the agent this only applies to currently-launching products, and it notes the manager-only extra section. There is no explicit statement of when not to use it or which sibling to prefer for board-wide data (e.g. list_launches).

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