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

Beyond the read-only/idempotent annotations, the description discloses real behavioral traits: that header values, the request body, and the heartbeat token are never returned, and that user-authored text fields must be treated as data rather than instructions. The injection warning is exactly the kind of safety context annotations cannot convey, and it directly affects how an agent should consume the response.

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 returned-field inventory, followed by the redaction boundary and the data-vs-instructions caution. Every sentence adds distinct information with no repetition of the tool name or schema.

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 does substantial work: it enumerates the returned fields and explicitly carves out what is withheld. A brief note on response shape or behavior when the monitor_id is unknown would close the remaining gap, but nothing essential is missing.

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?

With a single parameter and 100% schema description coverage ('Monitor id from monitor_list'), the schema already carries the semantics. The description adds no format, range, or resolution guidance for monitor_id beyond what is structured, 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?

The description names the resource ('one monitor') and enumerates exactly what detail it returns: target, type, interval, regions, alert switches, keyword and API check settings. That enumeration distinguishes it from monitor_list by making clear this is the single-record detail view, though the verb is only implicit ('One monitor in detail').

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 only implied: fetching 'one monitor in detail' naturally contrasts with monitor_list, and the input schema's note that monitor_id comes from monitor_list reinforces the workflow. But the description never says when to use this versus monitor_list or any other sibling, and offers no exclusions or prerequisites.

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