Get a Monitor

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful content about what data comes back (baseline, latest run, latest event, next schedule), which is meaningful beyond the annotations, though it omits any detail on error behavior or what happens for a nonexistent id.

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?

A single tight sentence that front-loads the resource and lists the returned facets with no filler. Efficient, though extremely terse for a tool whose parameters are entirely undocumented.

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 simple read-only tool with no output schema, the description usefully previews the returned fields and annotations cover safety. However, the total absence of parameter explanation for both id and debug leaves a real gap for correct invocation.

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 0% for two parameters, and the description never mentions 'id' or 'debug'. With low coverage the description is expected to compensate, but it provides no hint about what the id refers to (monitor UUID, slug, etc.) or what debug does.

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 a specific resource (Monitor) and enumerates the facets it retrieves (baseline, latest run, latest event, next schedule). 'Check' is a slightly soft verb, but the returned-fields list makes the intent concrete and separates it from list_monitors, get_monitor_run, and create_monitor.

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?

There is no guidance on when to use this tool versus siblings like get_monitor_run, list_monitors, or preview_monitor, and no prerequisites or exclusions are stated. The agent must infer usage from the name alone.

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