list_wordlists

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

No annotations exist, so the description is solely responsible. It states 'Returns directory listings' but does not disclose details like recursion depth, size limits, authentication, or output format. Behavior is straightforward but lacks depth.

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: first states purpose and resource, second lists use cases. Front-loaded and efficient with no redundant information.

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 no output schema and no annotations, the description explains the tool's action (browsing categories, returning directory listings) and use cases. It lacks details on return structure, but for a browsing tool it is reasonably complete.

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 100% and both parameters have descriptions (enum for category, optional for subdirectory). The description adds use-case context but no extra parameter-level meaning beyond the schema.

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 browses SecLists wordlists by category and lists use cases like directory brute-forcing, subdomain enumeration, etc., making the purpose specific and distinct from sibling tools such as 'search_wordlists' and 'get_wordlist'.

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 implies usage for exploring categories but does not explicitly state when to use this tool versus alternatives like 'search_wordlists' or 'get_wordlist'. No when-not-to-use or alternative naming is provided.

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