htb_list_sherlocks

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

No annotations exist. The description does not disclose behavioral traits such as read-only nature, pagination behavior, rate limits, or what the response includes. It only mentions 'optional filters' without elaborating on behavior.

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 sentence, but it is under-specified. While concise, it sacrifices necessary detail. A balanced description would be slightly longer to cover key parameters and usage context.

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 listing tool with 9 parameters and no output schema, the description is insufficient. It fails to explain how filters combine, pagination defaults, or expected output format. More complete documentation is needed for effective use.

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 0%. The description adds meaning only to 'category' (comma-separated ids). The other 8 parameters (page, state, status, etc.) receive no explanation, leaving the agent to infer from field names 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 'List Sherlocks with optional filters.' The verb 'List' and resource 'Sherlocks' are specific, distinguishing it from sibling list tools like 'htb_list_machines' or 'htb_list_challenges'.

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?

No guidance on when to use this tool versus alternatives (e.g., 'htb_sherlock_info', 'htb_sherlock_tasks'). No when-not-to-use or comparison with other list tools is provided.

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