check_http_endpoint

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool does (connectivity testing, response time measurement, status code validation) but doesn't mention important behavioral aspects like whether it follows redirects, handles authentication, includes request bodies, or what happens on timeout. The description adds value but leaves gaps for a monitoring tool.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core functionality, and the second provides usage context. No wasted words, and the most important information (what the tool does) is front-loaded.

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 monitoring tool with 5 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It covers the 'what' but lacks details about behavioral characteristics, error handling, and output format. The 100% schema coverage helps, but the description should do more to compensate for the lack of annotations and output schema.

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?

The description doesn't add any parameter-specific information beyond what's already in the schema (which has 100% coverage). It mentions general capabilities like 'measure response time' and 'validate status codes' which relate to the timeout and expectedStatus parameters, but doesn't provide additional semantic context about how these parameters interact or affect 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 the tool's purpose with specific verbs ('check', 'test connectivity', 'measure response time', 'validate status codes') and resources ('HTTP/HTTPS endpoint', 'APIs, websites, and web services'). It distinguishes what the tool does from a simple ping by mentioning multiple validation aspects.

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 provides implied usage context ('Perfect for monitoring APIs, websites, and web services') but doesn't explicitly state when to use this tool versus alternatives. With no sibling tools mentioned, this is adequate but lacks explicit guidance about scenarios where this tool might not be appropriate.

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