search_wordlists

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

No annotations are provided, so the description carries the full burden. It implies a read-only search operation but does not disclose details such as the return format, whether multiple results are returned, or any side effects. It adds some context by mentioning 'SecLists' and 'filename or keyword' but lacks behavioral traits like pagination or rate limits.

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 consists of two concise sentences with no filler. It is front-loaded with the action ('Search for wordlists') and directly states the use case. Every word adds value.

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?

The tool has no output schema, so the description could clarify what the tool returns (e.g., list of filenames, paths). It does not mention whether results are ordered, limited, or paginated. Given the context of sibling tools like 'get_recommended_wordlist', users might expect more detail about output format.

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 input schema covers 100% of parameters with descriptions, but the tool description adds concrete examples for both parameters: 'e.g., 'common', 'api', 'subdomain', 'sqli', 'traversal' for query and 'like 'Discovery', 'Fuzzing', 'Passwords' for category. This enriches the semantics beyond the schema alone.

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 tool's purpose: search for wordlists by filename or keyword. It distinguishes itself from sibling tools like 'list_wordlists' (which likely lists all) and 'get_wordlist' (which retrieves a specific one) by specifying that it's for finding the right wordlist for a specific testing task.

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 clear guidance on when to use the tool: 'Use this to find the right wordlist for a specific testing task.' It implies a search context but does not explicitly state when not to use it or compare with alternatives like 'list_wordlists' or 'get_recommended_wordlist'.

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