htb_sherlock_info

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

With no annotations, the description should disclose behavioral traits. It implies a read-only operation by stating 'return', but does not mention side effects, authentication requirements, or rate limits. The vague 'details' leaves the agent guessing about scope.

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, unambiguous sentence with 8 words. Every word is necessary, and it is perfectly front-loaded with the core action. No superfluous 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 the lack of output schema, the description should hint at what 'details' includes (e.g., name, difficulty, status). It omits this entirely, leaving the agent uninformed about the response structure. Simple tool but insufficient for a single-param query.

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?

Despite 0% schema description coverage, the description adds meaning by specifying that the 'sherlock' parameter accepts 'id or slug/name'. This clarifies the acceptable input format beyond the schema's bare 'type: string'.

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 action ('return Sherlock details') and the identification method ('by id or slug/name'). It distinguishes the tool from siblings like htb_sherlock_tasks or htb_sherlock_progress by focusing on general details. However, it doesn't explicitly contrast with them.

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 is given on when to use this tool versus alternatives such as htb_sherlock_tasks or htb_sherlock_play. The description provides no context about prerequisites or preferred usage scenarios.

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