create_digest_watch

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

With no annotations, the description discloses key behaviors: costs 1 credit, watch lasts 90 days, fires with curated summary regardless of dramatic changes. Missing details on whether it's a write operation, but sufficient for a simple registration tool.

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?

Three concise sentences with front-loaded purpose, followed by cost, lifetime, and use case. No redundant information.

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?

Covers main aspects (cadence, webhook nature, cost, lifetime) but lacks mention of return value (e.g., watch ID) or webhook payload structure. Adequate for a tool with no output schema.

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 covers all parameters with 100% description coverage. Description adds context like 'curated summary' but does not provide additional semantics beyond schema (e.g., format of callback_url). Meets baseline but no extra value.

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?

Clearly states the tool registers a scheduled digest webhook for pricing changes with daily/weekly cadence. Distinguishes from realtime alternatives (set-and-forget) and mentions it fires regardless of drama, differing from siblings like create_price_watch.

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?

Implicitly tells agents to use this for periodic snapshots instead of realtime transitions. Notes cost and lifetime, but does not explicitly name alternative tools or state when not to use.

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