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

Annotations already declare read-only and idempotent behavior. The description adds account requirement and default sort order, which are useful. It doesn't contradict annotations and provides context on expected behavior (e.g., requiring authentication) beyond the annotation hints.

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, no fluff. The first sentence states the core action and sort, the second covers filtering and authentication. All content earns its place.

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, but the description sufficiently conveys that it returns a list of tasks with filter options. Given it's a straightforward list tool with good annotations, the description is adequate without explaining return format in detail.

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% with detailed parameter descriptions for limit, filter, and weddingId. The description adds the ordering detail ('newest deadlines first') but doesn't add meaning to the parameters themselves. Baseline 3 is appropriate.

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 clearly identifies the resource (tasks from the Wedyesday checklist) and the action (list), plus the default sort order (newest deadlines first). It distinguishes itself from sibling add/complete tools by indicating it's a read operation on tasks.

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 states a prerequisite (connected account) and explains filtering options for different states (overdue, due soon, done). It doesn't explicitly exclude alternatives (e.g., 'use list_wedding_markets for vendor tasks'), but the purpose is clear enough for an agent to choose it over other list tools.

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