pentest_ctf_stego

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

With no annotations, the description carries the full burden, and it only discloses which underlying commands run. It does not state that the operation is read-only and non-destructive to the target file, whether external tooling must be installed, or how results from the three checks are combined or ordered. An agent gets the mechanics but not the safety or execution profile.

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?

One short fragment, front-loaded with the scope ('Stego quick checks') followed by the concrete tool list, with no filler. It is telegraphic to the point of being slightly cryptic, but nothing is wasted.

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?

There is no output schema, so the description should explain what the checks return (hidden data, embedded payload, matched keyword lines); it does not. Combined with no annotations and an undocumented path parameter, an agent knows the topic but not the call contract or the result shape.

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 0% for the single 'path' parameter, and the description never clarifies that it is a filesystem path to a local image/artifact to inspect. The PNG/BMP mention is the only indirect hint about acceptable inputs, and nothing covers relative vs absolute paths or how unsupported formats are handled.

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?

Names a concrete activity (stego checks) plus the specific underlying utilities (zsteg on PNG/BMP, steghide info, keyword strings), so an agent can tell it targets steganography in image files rather than generic extraction. It is distinguishable from generic siblings like pentest_ctf_strings or pentest_ctf_binwalk because it says 'stego'. It stops short of stating that it operates on a single file artifact.

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?

'quick checks' implies a triage role: run this early on a suspected stego image before deeper carving. However, no explicit alternatives are named, and the overlap with pentest_ctf_strings and pentest_ctf_binwalk is left for the agent to infer. There is no when-not-to-use guidance or prerequisite (e.g., a steghide passphrase).

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