osint-mcp-server

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 behavioral disclosure. It states the action and return value but lacks critical details: it doesn't mention rate limits, authentication needs, error handling, or whether the lookup is authoritative/cached. For a network tool with zero annotation coverage, this is a significant gap in transparency.

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 concise sentences with zero waste: the first defines the action and input, the second specifies the output. It is front-loaded with the core purpose and appropriately sized for a simple lookup tool, making it easy to parse quickly.

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 tool's low complexity (single parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose and return value but lacks behavioral context (e.g., network dependencies, error cases). For a straightforward lookup tool, this is adequate but leaves gaps that could hinder reliable agent invocation.

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%, with the single parameter 'ip' documented as 'IP address for reverse lookup'. The description adds no additional semantic context beyond this (e.g., format examples like IPv4 vs. IPv6, validation rules). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 specific action ('Perform reverse DNS (PTR) lookup') and resource ('for an IP address'), distinguishing it from sibling tools like 'dns_lookup' (forward lookup) and 'hackertarget_reverseip' (similar but from a different source). It explicitly mentions the return value ('associated hostnames'), making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'hackertarget_reverseip' or 'shodan_dns_resolve' that might offer similar functionality, nor does it specify use cases, prerequisites, or exclusions (e.g., IPv4 vs. IPv6, rate limits). Usage is implied by the action but not explicitly defined.

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