Raw HTB API Call

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context beyond that — default v4 base URL, v5 override, leading-slash tolerance, raw JSON body format, binary-output saving, and relative-path resolution under the toolkit directory. It stops short of stating auth requirements or error/status handling for a tool that can issue DELETE/POST, which keeps it out of the top band.

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?

Front-loads the escape-hatch purpose and the routing condition, then packs concrete usage details. It is dense and multi-clause, but each sentence carries actionable information; the baseUrl and output sentences in particular are not padding.

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 5-parameter, untyped passthrough with no output schema, the description covers base URL selection, path/data formats, and binary-output behavior — enough to invoke it correctly. Remaining gaps (auth expectations, behavior on non-2xx responses) are real but secondary given the openWorld annotation.

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% so the baseline is 3, but the description genuinely adds meaning: baseUrl is explained as the v5 override, data as a raw JSON string, output as a binary-save target with relative paths resolved under the toolkit directory, and path's optional leading slash. These are semantics not present in the schema text.

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?

States a specific verb+resource ('call any HTB API endpoint directly') and frames itself as an 'escape hatch', which cleanly separates it from the typed siblings like htb_machine_list or htb_challenge_info. An agent can identify its role without opening the schema.

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?

Gives an explicit routing rule: 'Use when a typed tool is missing or an endpoint moved.' That is precisely the when-to-use condition that distinguishes this fallback from the ~21 typed siblings, leaving nothing to inference.

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