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

No annotations are provided, so the description carries the full burden of explaining behavior. It only states what the tool targets (external scripts without integrity=) but does not disclose how it works, whether it makes network requests, returns a list, or has side effects. An agent cannot infer the operational behavior from this sparse text.

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 very short, which is concise, but it is a fragment rather than a clear sentence. It repeats the tool name and uses a confusing colon structure. While it earns points for brevity, it sacrifices necessary detail, making it less effective than a well-structured one-liner.

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?

With one parameter and no parameter description, the agent cannot determine how to invoke the tool correctly. Even though an output schema exists, the input requirements are entirely unspecified. For a security-check tool that likely takes a URL or domain, this is a significant 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 a single parameter 'q' with no description, and schema description coverage is 0%. The tool description never mentions 'q' or what value it should contain (likely a URL or domain). Since the description does not compensate for the schema's lack of coverage, the agent has no clues about parameter semantics.

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 the tool checks for Subresource Integrity issues, specifically external scripts lacking an integrity attribute. This is a specific verb ('Check') and resource, which makes the core purpose clear. However, it doesn't distinguish it from sibling security tools like csp_parse or headers, so it falls short of a 5.

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?

There is no guidance on when to use this tool instead of other security checks, nor any indication of what input format (e.g., a URL) is expected. The description offers no context about typical use cases or prerequisites, leaving the agent without direction.

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