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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the bar is lower. The description adds valuable context by listing return fields (status, hiddenReason, removedReason, aiDisclosure, tokenCard) and noting that a session is needed for restricted visibility, though it lacks rate-limit or error behavior details.

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?

The description is a single, front-loaded sentence that packs the core action, endpoint, return fields, and session condition with no wasted words. It is appropriately sized for the tool's complexity.

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?

Given no output schema, the description helpfully enumerates key return fields and explains the session's role for seeing restricted content. It covers the essential information an agent needs to call correctly, though it omits error handling or pagination details.

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?

With 50% schema coverage, the session parameter is documented in the schema, but the description adds the purpose of passing it (to see draft/hidden/removed reels). The reelId parameter is not described beyond its name and endpoint path, so the description only partially compensates for the coverage gap.

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 clear verb ('poll') and resource ('one reel'), and includes the endpoint GET /api/reels/<reelId>, making it easy to distinguish from memeswap_reel_post. It does not explicitly name an alternative sibling, so it falls 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?

It says 'Use to poll one reel' and specifies that passing the creator session reveals draft, hidden, or removed reels, giving clear context for invocation. However, it offers no when-not-to-use guidance or explicit alternatives, which a 5 would require.

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