net_gzip_check

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

With no annotations provided, the description must carry behavioral disclosure. It describes the core purpose (gzip check and size comparison) but does not mention that it likely makes an HTTP request, whether it is read-only, or how it handles servers without gzip. This leaves important behavioral aspects unstated.

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 that efficiently conveys the tool's purpose, with 'Gzip' front-loaded. There is no fluff or redundancy; every word contributes to 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?

For a one-parameter network check with no output schema and no annotations, the description covers the primary purpose but leaves out operational specifics such as return format, error handling, or network behavior. The description is adequate but not comprehensive.

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 one parameter, 'url', with no description (0% coverage). The tool description does not explicitly define the parameter or its format beyond implying the target is a server. This offers minimal additional meaning beyond the property name itself.

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 a specific action (check) and a resource (whether the server enables gzip and compression size comparison). It is distinct from sibling network tools like net_url_status or net_fetch, making it easy to identify when this tool should be used.

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 usage is implied by the name and description – it is for checking gzip compression on a server. However, no explicit guidance is given about when to prefer this over alternatives like net_url_status or net_fetch, nor are exclusions mentioned.

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