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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not required to restate safety. It adds context by specifying that results are recent, HTTP/TLS-oriented, and limited to 1–500, which is useful. However, it does not disclose what 'recent' means, how results are ordered, or any pagination behavior beyond the limit.

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?

The description is only two short sentences. The action and purpose come first, and the limit detail is front-loaded efficiently. There is no filler, redundancy, or unnecessary elaboration.

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?

The presence of an output schema and safety annotations reduces the burden on the description. Still, the description omits guidance for choosing this tool among several health-related siblings and fails to document the required agent_id. It is adequate for a straightforward read operation but not 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 description coverage is 0%, so the description must compensate. It only adds meaning to the limit parameter ('Limit 1–500') and leaves the required agent_id parameter completely unaddressed. This is insufficient for a 2-parameter tool with zero schema-level documentation.

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 states a clear action ('Read'), a specific resource ('recent HTTP/TLS results'), and a purpose ('to diagnose failures'). This is more specific than a tautology and gives the agent a concrete idea of what the tool does, though it does not explicitly distinguish it from siblings like agent_health_status or agent_health_heartbeat.

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 phrase 'to diagnose failures' implies a use case, but the description does not explicitly say when to use this tool versus alternatives, nor does it mention any exclusions. With multiple health-related sibling tools, an agent could still be unsure whether to pick this over agent_health_status or agent_health_heartbeat.

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