webcheck_security

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral details such as how the bundle aggregates results, execution order, concurrency, or error handling. For a multi-check tool, this is a significant gap.

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 lists the bundled security checks. It is front-loaded with 'Security bundle' and avoids unnecessary words. While minimal, it serves its purpose without waste.

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 complexity (multiple checks) and lack of an output schema, the description is under-specified. It does not explain how results are structured, whether responses aggregate all checks or are separate, or how to interpret failures. More context is needed for an agent to confidently rely on this tool.

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 description coverage is 80%, with url, timeout, base_url, and max_chars documented. The tool description does not add parameter meaning beyond the schema. The undocumented max_workers parameter remains unexplained in both the schema and description, keeping the score at baseline.

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 identifies the tool as a 'Security bundle' listing specific checks (ssl, tls, hsts, etc.), which distinguishes it from individual sibling tools like webcheck_ssl and webcheck_dns. It lacks an explicit verb like 'runs' or 'checks', but the intent is clear.

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 usage guidance is provided. The description does not indicate when to prefer this bundle over individual security tools, nor does it mention any trade-offs or prerequisites. This is a missed opportunity given the sibling tools.

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