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

With no annotations, the description carries the full behavioral burden, and "Runs the same code the tool page runs" is an opaque implementation note rather than usable context. Nothing is said about what the response contains (a list of offending resources? a boolean?), whether it requires a reachable external URL, or any rate/side-effect characteristics.

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?

It is brief, but brevity here is under-specification rather than conciseness: three disconnected fragments with no verb, and "Runs the same code the tool page runs" / "Scope: check" consume space without conveying usable information. It is not front-loaded with what the tool does.

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 simple single-parameter check with no output schema, the description should at least state what is inspected and roughly what comes back; it does neither. The one clarifying sentence it does contain is unhelpfully vague, leaving the agent to guess at behavior.

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 100% and there is a single required parameter (url) already documented as "Full URL including scheme." The description adds no further meaning about format, scheme requirements, or how the target page is fetched, so the baseline of 3 applies.

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?

"Mixed content on an HTTPS page" identifies the resource/topic, and the name plus this fragment let an agent infer it detects mixed-content issues, but there is no verb phrase stating what the tool actually does (detect? list? report?). It is a topic label, not a purpose statement, and does not distinguish itself from neighbors such as check_security or check_csp.

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 when-to-use or when-not-to-use guidance is given; "Scope: check" is not an actionable instruction. An agent has no signal on when to pick this over check_security, check_csp, or check_protocol, which likely overlap.

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