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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds a genuinely useful behavioral note that the tool is free during beta and charging is disabled. It stops short of describing what a monitor does operationally (persistence, ownership, alert delivery), which a mutation tool with annotations could still benefit from.

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 tight sentences with the purpose front-loaded and the usage condition immediately after. The beta/pricing clause is relevant but slightly tangential to invocation, keeping it just short of ideal.

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 three-parameter creation tool with no output schema and no auth/permission annotations, the description covers purpose and trigger but leaves gaps: ownership semantics, whether creation is idempotent, and how a created monitor is identified. Adequate to make the call, incomplete for the mutation it performs.

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 0% across three parameters, so the description carries the full burden and largely fails to. It gestures at score/risk-band/decision changes, loosely implying score_drop_threshold, but never explains subject_agent_id versus owner_agent_id or what happens if owner_agent_id is omitted.

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 ('Create continuous monitoring') and scopes it to 'one agent counterparty,' which is clear and actionable. No sibling tool offers comparable monitoring, so explicit differentiation isn't required, but the description doesn't distinguish itself from the broader trust-verification siblings either.

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 a concrete trigger condition — 'Use when an agent wants recurring alerts if the counterparty score, risk band, or decision changes materially' — which tells the agent exactly when this tool fits. It does not name alternatives (e.g., trust_before_action for one-off checks), so there is no explicit when-not guidance.

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