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

With no annotations present, the description must carry the full behavioral disclosure burden. It tells the agent the tool is about hidden PNG text chunks but never states what operation it performs, whether it extracts/decodes them, or what limitations exist around zTXt/iTXt handling.

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 a single compact, front-loaded phrase with no wasted words, and the colon-plus-parenthetical structure is easy to parse. It is concise to the point of being sparse, but structurally it is clean 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?

Despite the tool being simple (one optional parameter) and having an output schema, the description does not explain the input format, the exact extraction behavior, or what the returned chunks will look like. An agent cannot confidently call this tool correctly based on the description alone.

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 single parameter 'q' has zero schema description coverage, and the description does not mention it at all. The agent is left completely unguided about what 'q' should be (URL, base64 data, file path, etc.), and the description provides no compensation for that gap.

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 names a specific resource ('PNG Chunks') and a precise target ('tEXt/zTXt/iTXt'), which clearly differentiates it from sibling image tools like imageexif, imagemeta, and imagelsb. It lacks an explicit verb such as 'extract' or 'reveal', so it stops just short of the strongest possible purpose statement.

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?

Use for hidden-text/steganography analysis of PNG chunks is implied by the description, especially with terms like 'Hidden' and 'steganography'. However, there is no explicit statement of when to prefer this tool over other image-analysis siblings, and no exclusions are given.

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