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

No annotations are provided, so the description carries the full burden. 'Reads' signals read-only behavior, 'Free' discloses the cost profile, and the return contents are spelled out in detail. It does not cover edge behavior such as an expired monitor or an empty run history, but the core behavioral profile is clearly disclosed and nothing contradicts the absent 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?

Three tight sentences with the main verb and resource front-loaded. The long middle sentence earns its length by compressing a full return contract through the reference to citation_tracker_check's rows plus changed_since_last, rather than restating everything. 'Free' and 'Needs the monitor_id' are zero-waste cost and precondition signals.

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 no output schema, the description correctly takes responsibility for explaining return values: remaining runs, next run time, most-recent-first ordering, per-engine rows, and changed_since_last. The single parameter is fully documented in the schema. The only omissions are edge-case behaviors (expired monitors, exhausted run lists), which is minor for a simple status read.

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 coverage is 100% and the monitor_id definition is already rich: pattern, length bounds, provenance (returned by monitor_7 or _30), and a credential warning. The description only repeats the requirement with 'Needs the monitor_id,' adding no semantic value beyond the baseline for a fully covered 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?

Opens with a specific verb ('Reads') plus a resource ('a monitor') and enumerates exactly what is returned: remaining runs, next run time, and run history. It also distinguishes itself from the sibling citation_tracker_check by stating its output is the same per-engine rows plus changed_since_last, so an agent can tell them apart without opening schemas.

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?

States the precondition 'Needs the monitor_id,' and the schema adds that this id comes from citation_tracker_monitor_7 or _30, telling the agent the tool only applies once a monitor has been created. It also discloses that it is 'Free.' It stops short of explicitly naming alternatives or exclusion conditions (e.g., use monitor_cancel to stop, or citation_tracker_check for one-off checks), which keeps this at a 4 rather than a 5.

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