Check HTTP Target

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

The description adds meaningful behavioral context beyond the annotations, such as DNS-pinned SSRF protection, bounded redirects/body reads, response assertions, and TLS-expiry diagnostics. These details inform the agent about safety measures and diagnostic capabilities, which is valuable. The annotations already declare read-only and non-destructive, so the bar is lower, but the description still provides additional useful context.

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 a single, focused sentence that conveys the core action and key features. It is front-loaded with the main purpose, though the technical jargon (e.g., 'DNS-pinned SSRF') might be dense. Every phrase adds value, so it earns a high score.

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?

Given no output schema, the description sufficiently explains what the tool does and what behaviors to expect (assertions, TLS diagnostics). It lacks explicit return format details, but for a read-only check tool with strong annotations, this is not a critical gap. The two-parameter schema is simple, and the description covers the core semantics.

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 50% (only 'name' is described). The description does not mention or explain the 'timeout_ms' parameter, leaving its semantics undocumented in both schema and description. The description's mention of 'bounded redirects/body reads' only indirectly relates to timeout behavior, but it does not clarify how the parameter affects the check.

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 clearly states 'Check a registered HTTP target' with a specific verb and resource, and enumerates distinct capabilities like SSRF protection and response assertions. This distinguishes it from sibling tools like check_server or check_github_actions, which target different resource types.

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 description implies the tool is for checking registered HTTP targets, but it does not explicitly state when to use it over alternatives or when not to use it. It lacks explicit exclusions or alternative tool references, relying on the name and context to convey usage.

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