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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint=false, so the description earns credit mainly for adding the auth scope requirement ('Requires monitor scope'), the cost profile ('free'), and the enumerated return surface, which matters because no output schema exists. 'Does not run monitoring or increase its budget' largely restates the read-only annotation, which keeps this at a 4 rather than 5.

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 short sentences, front-loaded with the verb and scope, then prerequisites/cost, then the boundary condition. No filler and nothing buried.

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 single-parameter read tool with no output schema, the description covers scope, cost, side-effect boundary and the returned fields, which is close to everything an agent needs. It does not say what happens when the id is unknown or not owned, a minor remaining gap.

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 single id parameter is already documented there, including its provenance from monitor_case. The description only adds the implicit constraint that the monitor must be owned by the caller; otherwise the schema carries the parameter semantics, so 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?

States a specific verb ('Read') and resource ('owned monitor'), then enumerates exactly what is returned (action, cadence, expiry, budget, nextRunAt, status, pauseReason). The closing negation 'Does not run monitoring' separates it from monitor_case without requiring the agent to open either schema.

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?

Gives two concrete usage facts: it requires monitor scope and is free, plus a negative boundary ('does not run monitoring or increase its budget'). It stops short of naming an alternative tool or an explicit when-to-use-instead-of-pause/resume_monitor condition, so it is clear context rather than full routing guidance.

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