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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states a high-level function. It does not explain limitations, what data is returned, whether the tool queries external feeds, or any side effects or rate considerations, leaving the agent to infer behavior.

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 brief, but it is under-specified rather than concise. The fragment 'Phishing Intel:' merely restates the title, and the remaining phrase is a terse label rather than a complete, informative sentence that earns its place.

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 ambiguous parameter and lack of usage guidance, the description is not complete enough for an agent to invoke the tool correctly. The output schema reduces the need for return-value descriptions, but the agent still lacks critical input and selection context.

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 single parameter q has 0% schema coverage, and the description only indirectly suggests that q relates to URL detection. It does not clarify whether q expects a URL, domain, IP, hash, or keyword, and it does not explain the default value or what an empty query would do.

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 names a specific resource ('phishing kit tracking') and actions ('URL detection'), so the agent knows what domain the tool operates in. It does not differentiate from closely related siblings like openphish or urlscan, but the core purpose is clearly stated.

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 is provided on when to use phishing_intel versus alternatives such as openphish, urlscan, threatcrowd, or botnet_tracker. The description gives no context about the expected input format or the conditions under which this tool should be selected.

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