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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by limiting scope to non-deleted monitors in the authenticated organization and by stating that it returns configuration rather than history or notification routing.

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?

The description is two sentences and front-loads what the tool returns before stating what it does not return. The first sentence is dense with a long list of configuration elements, but every item appears relevant and there is no filler.

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 one-parameter read-only tool with full schema coverage and rich annotations, the description is largely complete: it explains returned configuration, excludes history and notification routing, and scopes the result to the authenticated organization. A minor gap is that it does not address the neighboring monitor_get tool or error behavior for missing or deleted monitors.

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%, so the single monitorExternalId parameter is already fully documented with its UUID format and source from MonitorList or MonitorListRecent. The description does not add parameter-specific syntax or format details beyond that, so it meets the baseline where the schema carries parameter semantics.

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: getting a non-deleted monitor's request/response configuration, timing, regions, SSL verification, and telemetry-environment links. It also distinguishes this configuration tool from sibling tools that return check history or notification routing, so an agent can identify its role without opening the 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?

The description gives clear usage context and explicitly names alternatives for excluded data: MonitorLatestChecks for check history and MonitorNotificationsGet for notification routing. It does not clarify how this differs from the close sibling monitor_get, which leaves some ambiguity, but the when-not guidance is strong.

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