network/curl

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 mentions 'native HTTP client' but does not disclose important behaviors such as following redirects, handling cookies, or default method (likely GET). It does not mention authentication handling or potential side effects (e.g., making external calls), but for a data transfer tool, the description is adequate though not rich. There is no contradiction with annotations since none exist.

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 concise sentence that front-loads the core purpose. There is no wasted text, and it is easily digestible for an agent. It earns its place by stating the verb and resource, though it could add more detail without becoming bloated.

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 the tool's moderate complexity (7 params, nested headers object) and no output schema, the description is somewhat thin. It does not explain return value structure (e.g., status code, truncated field), but the schema's max_body description mentions truncated: true, hinting at output. It lacks guidance on error handling or default behaviors, but for a simple HTTP client, it is minimally complete for basic calls.

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 57%, so the description should compensate for undocumented parameters. The description adds the word 'native' and 'HTTP', but does not explain key parameters like method, timeout, or max_body in detail. However, the schema has descriptions for body, headers, insecure, and max_body, which cover most params. The method param has no description, and the description does not clarify it, but the baseline is 3 and the description adds a little value, so 4 is appropriate for partial compensation.

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 verb ('Transfer') and resource ('data from a URL'), distinguishing it from sibling network tools like ping, nslookup, and trace-path, which are also network-related but serve different purposes. It is concise and unambiguous, though it does not explicitly mention that it supports multiple HTTP methods, which is implied by the presence of a method parameter.

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 no explicit guidance on when to use this tool versus alternatives. It implies usage for HTTP requests, but does not mention exclusions (e.g., not for file transfers via SCP) or alternatives like files/read for local files. Given the sibling tools are diverse, more guidance would be helpful, but the description is not misleading.

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