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

Annotations already declare readOnlyHint=true, so the description earns credit for going further: it enumerates what the response contains (current status, last_checked_at, SSL/HTTP settings, regions, alerting configuration) and cites the underlying endpoint. It stops short of noting error behavior for missing ids, but the read-only safety profile is fully covered.

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 returned fields come first, then the API mapping. No filler, nothing to trim.

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?

A single-param read tool with no output schema, and the description compensates by summarizing the response payload. What is missing is minor: behavior when the id does not exist or the monitor is not visible to the caller.

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 coverage is 100%, and the schema already explains that monitor_id comes from betterstack_list_monitors. The description only says 'by id' and adds no format or sourcing detail beyond the schema, so the 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?

States a specific verb and resource ('Get a single monitor by id') and enumerates the fields returned, so an agent knows exactly what it retrieves. It does not explicitly name betterstack_list_monitors as the alternative, but 'single monitor' implicitly separates it from the list tool.

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 implied ('single monitor by id' vs the list sibling), but there is no explicit statement of when to prefer this over betterstack_list_monitors or what happens if the id is unknown. The schema's parameter note points at the list tool as the id source, but that guidance is in the schema, not the description.

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