List search filters

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

Annotations already declare readOnlyHint: true, and the description aligns by stating it lists filters. It adds the example filters and the fact that it's a metadata lookup, but doesn't describe return format or any other behavior. Since this is a trivial read-only operation with no parameters, the description provides adequate but not exceptional 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?

Two sentences, front-loaded with the main action. The first sentence states function and examples; the second gives usage guidance. No redundant details.

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 zero-parameter, read-only list tool, the description fully covers its purpose and usage context. It doesn't have an output schema, but the description doesn't need to explain return values for a simple list of filter names. The sibling tools are all distinct, and this description positions the tool correctly.

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?

No parameters exist, and the input schema confirms an empty properties object. Per the rubric, 0 parameters yields a baseline of 4. The description doesn't need to explain any parameters.

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 uses a specific verb 'List' with a clear resource 'search filters Shodan supports,' and provides concrete examples (country, port, net, vuln, product). This clearly distinguishes it from sibling tools like shodan_search, which executes queries, while this is about filter metadata.

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?

Explicitly states when to use: 'before writing a shodan_search query' and purpose 'to confirm the right filter name.' This provides clear context for an AI agent. It doesn't explicitly mention alternatives or when not to use it, but the instruction is sufficient.

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