Catalog diff polling — added / removed endpoints since `since`

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

With no annotations provided, the description fully discloses behavioral traits: cost ($0.001 USDC), internal cron interval (5 min), and that faster polling yields unchanged data. It also explains the logical conditions for inclusion in added/removed lists.

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 compact 5 sentences, each delivering critical info. The main purpose is front-loaded. Slightly verbose in the pricing example, but still efficient.

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?

Despite lacking an output schema, the description enumerates all returned fields (added_endpoints, removed_endpoints, counts, polls_in_window, active totals) and explains behavior and constraints, making it fully informative for agent use.

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 input schema already covers both parameters with descriptions. The description adds value by stating defaults (since=now-24h, limit=200) and clarifying the limit applies independently to each list, enhancing understanding beyond 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 clearly states it is a 'polling-friendly catalog diff' that returns added and removed endpoints since a given timestamp, distinguishing it from sibling tools like the full catalog or subscription-based 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?

It explicitly recommends use for 'aggregator agents that need a fresh delta without re-pulling the whole catalog' and notes that polling more often than every 5 minutes returns identical data. However, it does not list specific alternative tools or conditions to avoid usage.

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