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

The description indicates a nondestructive, read-only operation (reputation check). With no annotations, it partially carries the burden. However, it lacks details on what the tool returns (e.g., a Boolean, score, or report), or any rate limits or authentication needs, leaving some transparency gaps.

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 two words plus a parenthetical. It is extremely concise and front-loads the essential information. Every word is meaningful with no 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 single parameter and lack of output schema, the description is too sparse. It does not explain what the 'check' returns (e.g., safe/unsafe label, risk score), or whether it supports batching or works for all URL types. For a security-critical tool, more detail is expected.

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 0%, so the description must compensate. It does not clarify the URL format (e.g., must include scheme). However, with only one required parameter named 'url', the tool's purpose is fairly obvious, earning a baseline of 3.

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 checks URL reputation for malware and phishing. It uses specific, relevant verbs and resource types, and the focus on security threats distinguishes it from sibling tools like 'search' or 'read'.

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 guidance on when to use this tool vs. alternatives is provided. While the context of reputation checking is clear, the description does not mention what kinds of URLs are supported, limitations, or when a different tool (e.g., 'search') would be more appropriate.

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