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

With no annotations, the description carries the full burden and does so thoroughly: it discloses pricing ($4.2, $0.6/check), non-refundability, non-recoverable monitor_id, cancellation, and 30-day retention. This is substantial behavioral context beyond what the input schema provides.

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?

Four sentences deliver the essential product facts without filler. The first sentence front-loads the core offering, and each subsequent sentence adds a distinct, material fact: execution timing, state retrieval, pricing/cancellation, and retention.

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?

Even without an output schema, the description names the returned artifacts (first run, monitor_id), the only credential, how to retrieve later runs, and the tool's limits. Combined with a fully described input schema, an agent has enough context to invoke and manage this tool correctly.

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%, and the schema already documents each parameter with constraints and examples. The description reinforces that cadence is daily/weekly and targets are 1-10 domains, but it does not add parameter-level semantics beyond the schema, so the baseline 3 applies.

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 and resource: 'Buys a monitor: 7 recurring runs of citation_tracker_check for one prompt and 1 to 10 target domains, daily or weekly.' This clearly distinguishes the tool from one-off check siblings and from the monitor_30 variant by run count.

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 gives explicit lifecycle guidance: the first run happens now, later runs are read via citation_tracker_monitor_status, and cancellation is done with citation_tracker_monitor_cancel. It does not explicitly contrast this with a one-time citation_tracker_check or the 30-run monitor, so it stops short of a full when-not-to-use statement.

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