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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered without description help. The description adds value by enumerating what is returned (status, response time, SSL state, maintenance mode), but says nothing about error cases, unknown IDs, or freshness of the data.

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 front-loaded sentence with no filler; the scope ('one check') precedes the field enumeration, and every clause carries information.

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 single-resource read with full annotation coverage, a 100%-covered one-param schema, and no output schema, the description's field enumeration is nearly sufficient. Only the lack of distinction from get_check_history/get_check_stats keeps it from being fully complete.

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% with a single well-documented check_id, so the schema carries parameter meaning. The description restates the scope ('one check') but adds no format, syntax, or sourcing detail beyond the schema's own note.

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 one check) and enumerates the returned fields, so the agent knows exactly what it retrieves. It implicitly distinguishes itself from list_checks by scoping to 'one check', but it never clarifies how it differs from siblings like get_check_history or get_check_stats.

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 only implied: the schema notes check_id comes from list_checks or create_check, which suggests a follow-up lookup after listing. There is no explicit when-to-use guidance or routing away from get_check_history/get_check_stats, leaving ambiguity about which detail tool to pick.

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