commix

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

No annotations are present, so the description carries the behavioral burden. It discloses that the tool detects and exploits command injection, supports results-based/blind/time-based techniques, and can open an interactive pseudo-shell on success. It stops short of warning about the potentially intrusive/destructive nature of exploitation, but the core behavior is clearly conveyed.

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?

Three sentences, each carrying distinct value: what it does, when to use it, and what the output looks like. There is no filler or repetition of schema fields.

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 two-parameter tool with full schema coverage and no output schema, the description covers purpose, selection criteria, injection techniques, and success output. It could be slightly more complete by noting prerequisites or a safety caveat, but nothing essential to invoking the tool correctly is missing.

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 100%, so the schema already documents the url and opts parameters, including a default value for opts. The description does not add parameter-level detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Automated OS command injection detection and exploitation tool.' It names the exact input surfaces (HTTP parameters, headers, cookies, POST data) and explicitly distinguishes itself from sqlmap, so an agent can identify what commix does 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?

It provides an explicit decision rule: 'Use when sqlmap confirms the parameter is NOT SQL injectable but may still be vulnerable to command injection.' This names the sibling tool and the condition that selects commix, and no other alternative is needed because commix is the dedicated command-injection tool in the sibling set.

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