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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, but the description adds genuinely new behavioral context: quota consumption, persistence of a receipt, and possible webhook delivery as a side effect. This is meaningful added value beyond the structured hints, though it stops short of describing authorization or failure behavior.

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?

Two compact sentences, front-loaded with the action and result, followed by the cost/side-effect disclosure. Every clause earns its place and nothing is repeated from the title.

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 side-effecting, non-idempotent action tool with no output schema, the description covers the success artifact ('change receipt'), the cost (quota), and the side effects (receipt stored, webhook fired). The remaining gap is the absence of any error or authorization expectation, but the core operational picture is complete.

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%, with both api_key and monitor_id documented in the schema, including the binding constraint that the monitor must belong to the calling key. The description adds nothing about parameter format or constraints, so the baseline of 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 states a specific verb and resource — run a monitor and return a source- and hash-bound change receipt — which is far more precise than the title alone. It implicitly distinguishes itself from read-oriented siblings like fluxproof_list_changes by declaring it is 'not an idempotent read,' though it never names an alternative tool to route to.

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?

Usage is implied by the effect disclosure ('consumes check quota, stores a receipt, may deliver a webhook'), which tells an agent the cost of calling it. However, there is no explicit when-to-use versus when-not-to-use guidance, and no alternative such as fluxproof_list_changes is named for the case where the agent only wants existing results.

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