commix

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

No annotations are provided, and the description does not disclose any behavioral traits. It does not state whether the tool is read-only or destructive, what authentication is required (beyond requiring a session_id), rate limits, or potential side effects like actually exploiting vulnerabilities. The agent is left blind to important safety and operational 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 extremely concise (one sentence), which is generally good for conciseness but insufficient for completeness. Every word is used, but critical information is missing, making the brevity a trade-off rather than an optimal structure.

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 complexity of a vulnerability scanner with two required parameters and no output schema, the description should explain the role of 'session_id', how results are returned, and how it differs from other vulnerability scanners. It fails to provide a complete picture for correct agent usage.

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?

The input schema has 0% description coverage, and the tool description does not explain the meaning of 'url' and 'session_id'. For example, 'session_id' is likely tied to an active session from a sibling tool like init_session, but no explanation is given. The description adds no value beyond the schema's parameter names.

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 'Command injection vulnerability scanner' clearly specifies the tool's purpose: it scans for command injection vulnerabilities. This verb-resource combination is distinct from sibling tools like sqlmap (SQL injection) and dalfox (XSS), making its purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. With 27 sibling tools all scanning for different vulnerabilities, an agent needs explicit context for when command injection scanning is appropriate versus other scanners. No prerequisites, when-not-to-use, or alternative suggestions are given.

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