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

Despite already having readOnlyHint=true and destructiveHint=false in annotations, the description enriches transparency by detailing server-side exclusion of past deadlines, sorting behavior, and the 'as_of' field representing the server-side cutoff. It also instructs to cite each record's originalUrl. This goes well beyond the bare annotations.

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 well-structured: a one-line summary, practical usage examples, source context, then explicit Args/Returns sections. Every sentence adds value—no fluff. It front-loads the core purpose and packs detailed behavior into a compact format.

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 only one optional parameter and no output schema, the description must explain the return structure, and it does: a dict with generated_at, as_of, platforms, total, and deadlines array with key fields. It also covers edge cases like 'rolling' deadlines. For a read-only listing tool, this is complete.

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?

The schema provides zero description for the 'platform' parameter (0% schema coverage). The description fully compensates by documenting it as 'Optional platform slug — amazon, shopify or tiktok-shop. Empty = all platforms.' and clearly explains the default behavior. This adds substantial meaning absent from the schema.

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 opens with a specific verb+resource statement: 'List upcoming seller-facing deadlines on Amazon, Shopify and/or TikTok Shop, soonest first.' It clearly states the platforms and ordering, and the examples ('any Amazon deadlines coming up') cement the purpose. While it doesn't explicitly contrast with the sibling tool, its scope is precise and unambiguous.

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 provides concrete example queries ('what do TikTok Shop sellers need to do before month end') and clarifies that deadlines come from official announcements, past deadlines are excluded, and free-form deadlines sort after dated ones. However, it doesn't explicitly mention alternatives or state when not to use this tool (e.g., for platform changes), so it falls short of a 5.

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