forensics_steghide

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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It only states 'Steganography with steghide or stegseek' without explaining side effects, required permissions, file handling, or possible actions such as brute-forcing or extraction. This is insufficient for an agent to anticipate consequences.

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 brief, which is concise, but it's under-specified rather than effectively concise. It consists of a single noun phrase without a verb, lacking essential information. The brevity does not serve the agent's understanding.

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 a complex tool with 6 parameters, no output schema, and no annotations, the one-line description is completely inadequate. It fails to explain the tool's purpose, behavior, or usage context, leaving the agent with no actionable information.

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?

With 6 parameters and 0% schema description coverage, the description needed to explain parameter semantics but doesn't. It doesn't mention 'file' as input, 'action' as operation type, 'wordlist' for stegseek brute-forcing, or any other parameter. The description adds no value beyond the schema field 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 'Steganography with steghide or stegseek' identifies the domain (steganography) and the underlying tools, but lacks an explicit verb or operation such as extract, embed, or inspect. It is vague about actual functionality and doesn't distinguish it from other forensic tools like binwalk or foremost.

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 provided on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or contrasting tools. The description offers no context for selection.

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