shodan_saved_queries

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

Annotations already declare readOnlyHint=true and destructiveHint=false, fully covering the safety profile. The description adds no behavioral context such as pagination behavior, rate limits, or what constitutes the 'directory'—it merely says 'browse'.

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 a single, front-loaded sentence with zero wasted words. It states the core action and resource concisely, which is appropriately sized for a simple read-only browse tool.

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 read-only tool with strong annotations and full schema coverage, the description is minimally adequate. However, it lacks any context about how 'saved search queries' are organized or when to use browsing versus the sibling search tool, leaving some gaps for an AI agent.

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%, so all three parameters (page, sort, order) have meaningful descriptions. The description itself adds no parameter information, but according to the baseline for high schema coverage, a score of 3 is appropriate.

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 'Browse the directory of saved search queries' uses a specific verb (browse) and resource (directory of saved search queries), making the tool's purpose clear. However, it does not explicitly distinguish itself from the sibling tool 'shodan_search_queries', which likely provides search functionality over the same resource.

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 offers no guidance on when to use this tool vs alternatives. It does not mention that 'shodan_search_queries' should be used for searching, nor any other context for choosing browsing over searching. This is a clear gap given the large sibling list.

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