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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: the auth scope requirement, the 'absent when empty' semantics of each collection, and the structural difference between a hook-fed parent monitor (repos with state, last run, 24-hour spend) and a repository monitor (parent_monitor_id, repo). This goes well beyond the annotation set.

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?

Front-loaded with the access requirement and purpose, then the field-by-field explanation. Dense but each clause carries information; the update_monitor/set_route comparison is slightly tangential but justified as a replace-vs-read warning.

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 present, the description carries the full burden of explaining the return payload and does so field by field (assertions, guards, routes, hook-fed vs repository shape, empty-set behavior). An agent has enough to interpret the response without further documentation.

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?

There is a single parameter with 100% schema description coverage ('Monitor UUID.'), so the schema already carries parameter meaning. The description adds no format, sourcing, or lookup detail for the id, making the baseline 3 appropriate.

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 and resource ('Gets one monitor by UUID with its full configuration'), which cleanly separates it from list_monitors and the run/trace tools in the sibling list. The scope of the returned payload is spelled out, so an agent knows exactly what it retrieves.

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 names a prerequisite ('Requires the read scope or higher') and explains the relationship to update_monitor / set_route by noting those replace whole sets while this result holds the current sets — an implicit 'read before you overwrite' cue. It never explicitly contrasts with list_monitors or get_run, so routing guidance is strong but not complete.

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