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

With readOnlyHint=true already declaring the safety profile and no output schema present, the description usefully discloses the shape of what comes back (latest event, latest invocations, passing status). It stops short of mentioning auth, rate limits, or error behavior, but it carries the return-value burden reasonably well.

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: the purpose and payload come first, the mental model second, and the API endpoint last. Nothing is wasted and nothing important is 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 read-only single-resource fetch with no output schema, the description covers the essentials including the returned fields. Slightly incomplete only on error/not-found behavior and whether the status is computed live versus cached.

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% for the single 'key' parameter, so the schema already documents it fully; the description adds no format or acquisition guidance (e.g. where to get the key). Baseline 3 is appropriate when the schema does the work.

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 ('Get full detail for one monitor') and enumerates the key payload contents (latest_event, latest_invocations, passing status), which cleanly separates it from cronitor_list_monitors and the mutation siblings.

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 framing 'is X healthy right now?' gives a clear situational context for when to reach for this tool, but it never names the alternatives (e.g. use cronitor_list_monitors for a roll-up) or any exclusions, so routing still requires inference.

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