list_images

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

With no annotations, the description carries the full burden and does disclose meaningful domain context: these are rendered schematics/drawings and filenames encode source document and PDF page. It says nothing about ordering, whether the set is complete, whether it can be empty, or that it is a read-only operation.

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 sentences, no padding, and the filename-encoding example is genuinely informative. It is not front-loaded with the action, however — the reader learns what the images are before learning that this returns a list of them.

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?

An output schema exists, so return values need not be explained, and the naming convention is covered. But for a no-annotation, no-parameter enumeration tool in a set containing get_image and get_source_page, the missing link between listing names and fetching an image leaves a real gap.

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 tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to explain and the description does not waste space on them.

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 is a noun phrase ('Names of the rendered schematic / drawing images') rather than a statement of what the tool does, so the verb (list/enumerate) must be inferred from the tool name. The resource is clear and specific, but there is no differentiation from get_image or the other list_* siblings.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of the obvious alternative get_image. An agent could infer that this is a discovery step preceding get_image, but that inference is never stated.

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