curl

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

The description mentions making POST requests, implying mutating behavior, which aligns with readOnlyHint: false. However, it does not disclose additional traits like rate limits, authentication, error handling, or response format, which are important for a generic HTTP 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 a single sentence with an example, immediately conveying the tool's purpose. It is concise without unnecessary detail, and the example aids understanding.

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 description lacks information about the return value, which is critical for an HTTP tool that returns responses (status, headers, body). It also does not cover error scenarios, timeouts, or authentication. Given no output schema, the description should fill this gap.

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 input schema has 100% description coverage for all four parameters. The tool description adds no extra meaning beyond what the schema provides, only giving a trivial example. Baseline 3 applies.

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 makes HTTP requests to web endpoints, with examples of GET and POST. This distinguishes it from sibling tools like ping or dig, as it is the only HTTP client. The verb 'Make HTTP requests' and resource 'web endpoints' are specific.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, given that no sibling tool offers HTTP request functionality, the usage is implied. No alternatives are mentioned.

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