Cdn Check

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

The description mentions that scanning may violate the CDN's terms, which adds behavioral nuance beyond the read-only annotation. It implies network probing but does not fully detail the exact requests or side effects, so it falls short of full transparency.

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 concise, consisting of two sentences that are well-structured and to the point. It efficiently conveys purpose and usage guidance without unnecessary verbosity.

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?

While the description covers purpose and usage advice, it does not describe the output format or any additional details an agent might need to interpret the results, leaving some contextual gaps.

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 schema defines a single required parameter 'target' with no description, and the tool description does not elaborate on its format or expected values. This leaves the parameter ambiguous and under-specified.

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: identifying hosts behind a CDN, WAF, or cloud provider. It also gives context on when it is useful, making the intent unambiguous.

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 explicitly recommends running this tool before any port scan and explains the reasoning, providing clear guidance on when to use it. It does not, however, mention alternative tools or conditions for not using it, so it is not a perfect 5.

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