steg_encode

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

Discloses LSB insertion and invisibility, but omits important behaviors like output format, image capacity limits, potential quality degradation, and requirement for steg_decode to retrieve data. Since no annotations exist, description could be more thorough.

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?

Single sentence efficiently conveys the core functionality. No wasted words.

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 steganography tool with no output schema, the description lacks return value details (e.g., encoded image format), capacity constraints, and prerequisites. It is minimally adequate but could better support correct invocation.

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 description adds limited value. It echoes parameter descriptions (e.g., 'secret text or binary', 'password for encryption') but does not provide additional syntax or format details beyond the schema.

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 clearly specifies the action (hide/inject), resource (PNG/BMP image pixel LSBs), and technique (steganography). It distinguishes itself from siblings like steg_decode and other unrelated tools.

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 explicit guidance on when to use this tool versus alternatives. No mention of prerequisites, limitations, or when not to use it (e.g., for non-image data, or if detection avoidance is critical).

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