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

Annotations cover the safety profile (readOnly/openWorld/non-destructive), and the description goes well beyond them: it decodes the status encoding (1 = passing, 0 = failing), explains firstdown, notes that full objects are 'scrubbed', and names the underlying GET /checks call. That is real added context, though response size/pagination behavior is unaddressed.

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?

Dense and front-loaded: the returned fields come first, then filtering, then the compact/detail switch, then the endpoint. Every clause carries information, with only minor slack in the parenthetical status decoding.

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?

With no output schema, the description correctly takes on the burden of describing the return shape, including field list, status encoding and firstdown semantics. Combined with full annotation coverage and 100% schema coverage, an agent has enough to call this correctly, missing only pagination/volume expectations.

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 all five params are already documented, which sets the baseline at 3. The description adds the notable detail that filtering happens 'client-side', but this sits in tension with the schema wording ('Only this check type'), so it adds ambiguity as much as clarification.

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 ('List monitoring checks') and enumerates the returned fields (label, type, target, interval, enabled state, pass/fail), which clearly separates it from the singular nodeping_get_check and from the summary/uptime/events siblings. An agent can identify this as the bulk-listing tool 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?

It says filtering is available 'by status, type or label text' and that detail=true switches to full objects, which implies when to use each mode. However it never states when to prefer this over nodeping_get_check, nodeping_get_check_summary or nodeping_get_current_events, so the selection guidance is only partially there.

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