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

With no annotations, the description must fully disclose behavior, but it only mentions 'no key' and lists output fields. It does not state that the input should be an IP address, what happens with invalid input, or any rate limits. The conflation of JARM and InternetDB is not resolved behaviorally.

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 short but poorly structured, repeating 'InternetDB' and mixing in 'JARM' without linking them. It reads as a label rather than a purpose statement. A clean structure like 'Query Shodan InternetDB for ports, CPEs, vulns, tags by IP (no key)' would earn a higher score.

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?

Despite having an output schema, the description leaves the central questions unanswered: what does the tool do, and what should be passed to 'q'? The agent cannot reliably invoke this tool correctly based on the available text. The output schema helps, but input semantics and tool purpose are missing.

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 coverage is 0% and the only parameter 'q' is entirely undocumented. The description provides no hint that 'q' expects an IP address, hostname, or something else. This is a critical gap for a single-parameter tool.

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 mixes 'JARM' and 'InternetDB' without stating a clear action or resource. It lists output fields (ports, CPEs, vulns, tags) but never explicitly says 'query' or 'lookup', leaving the tool's primary function ambiguous. The presence of an 'internetdb' sibling further muddies what this tool uniquely does.

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 given for when to prefer this tool over alternatives like 'internetdb' or other IP lookup tools. The only differentiator mentioned, '(no key)', is a feature but not a usage condition. An agent gets no help deciding between this and its siblings.

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