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

Annotations already cover the read-only/idempotent/non-destructive safety profile, and the description adds real context beyond them: the default today/overdue filtering, that the daily email triggers exactly this query, and what each result carries (account, day, topic, look, pieceId). It stops short of describing result volume or ordering, so not a full 5.

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?

Front-loaded with what is listed, then scope, then the includeUpcoming condition, then the pieceId next step. Dense and mostly earns its place, though the parenthetical list of user phrasings and the look-field aside add some length.

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?

For a read-only list tool with 100% schema coverage and no output schema, the description supplies everything needed: what is returned, the default filter, the opt-in flag semantics, and the downstream get_reel_playbook(pieceId) step.

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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description reinforces includeUpcoming's default behavior ('by default only the ones due TODAY or overdue'), but adds little beyond what the schema text already conveys.

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 verb (list) and resource (reels/long YouTube videos Autopilot planned and that are awaiting video production), with the exact fields returned. It also names the follow-up sibling get_reel_playbook, so an agent can distinguish this from other list tools without opening schemas.

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?

Explicitly says the default scope is due today/overdue, maps it to the user's likely phrasing ('make my pending Ignix reels'), and states the condition for the alternative (pass includeUpcoming only for later days). This is a complete when/when-not/alternative guide.

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