img_lsb_extract

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

No annotations provided, so description carries full burden. It states it extracts bits, attempts UTF-8 decode, and shows hex dump, but lacks details on failure behavior, performance, or side effects. Adequate but not 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?

Two concise sentences, no extraneous words. First sentence states purpose, second expands on behavior with key details (channels, bit plane, decode, hex dump). Front-loaded and efficient.

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 5 parameters, no output schema, and many siblings, description covers core functionality but omits output structure and error conditions. It adds value with decode and hex dump context, but could be more complete.

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 baseline is 3. Description adds context about extracting from specified channels and bit plane, but this closely mirrors schema descriptions. The mention of UTF-8 decode and hex dump relates to output, not parameter semantics.

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?

Description clearly states 'Extract hidden data from image LSBs', a specific verb+resource. It distinguishes from siblings like img_lsb_detect (detection) and img_lsb_embed (embedding) by focusing on extraction and mentioning output details like hex dump and UTF-8 decode.

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?

Description does not provide explicit when-to-use or when-not-to-use guidance. Usage is implied for extraction of hidden LSB data, but no comparison with alternatives like img_lsb_detect or prerequisites are mentioned.

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