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

Beyond the readOnlyHint annotation, the description discloses ordering (newest first), the backfill flag and its implications for email, and the presence of episode/podcast slugs that feed other tools. These are genuinely useful behavioral details not visible in the schema or 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 compact, front-loaded with the core action, and every clause adds information. It avoids restating schema details and packs ordering, backfill behavior, parameter guidance, and downstream tool links into two efficient sentences.

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 no output schema, the description covers what the response contains, how to get more detail, how to filter by date, and how returned slugs connect to other tools. Pagination and formatting defaults are already fully specified in the input schema, so nothing essential is missing.

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 the schema already documents all parameters. The description adds value by explaining how view=detailed changes the payload, how after/before scope results, and why the slugs matter. This goes slightly beyond the baseline for fully documented schemas.

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 begins with a precise verb and resource: 'List the matches an alert has caught, newest first'. It clearly distinguishes matches from the alert itself, and the 'payoff of an alert' phrase makes the tool's role obvious relative to sibling alert tools.

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?

The description gives clear context for when this tool is relevant: after an alert has caught matches, and it explains downstream use of the slugs. It does not explicitly name alternative tools to exclude, but the context is specific enough that an agent would not confuse it with alert listing or podcast transcript search.

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