arcane_list_images

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says 'list', which implies a read-only operation, but it does not confirm this, nor does it mention pagination, sorting, authentication requirements, rate limits, or the exact return format. This is a significant gap for a tool with no annotation context.

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 concise sentence of six words, with no redundancy or filler. It front-loads the action and resource, making it immediately scannable. Every word earns its place, and it is appropriately sized given the tool's simplicity.

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 the simple schema (2 params, no nested objects) and lack of output schema, the description is minimally viable. It clearly states the core function, but it omits important context like what the list contains (image IDs? full objects?), whether there is pagination, and how the search parameter interacts with the environment. For a tool with no annotations and no output schema, the description should provide more completion.

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% with descriptions for both parameters (search and environmentId). The description does not add any extra semantic meaning beyond the schema; it only repeats that images are listed 'in an environment', which already corresponds to the environmentId parameter. Baseline of 3 is appropriate since the schema handles parameter documentation.

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 'List images in an environment' clearly states the action (list) and resource (images), with a scope (environment). It is specific enough to distinguish from sibling tools like arcane_get_image (singular) or arcane_pull_image. However, it could be slightly more explicit about whether it returns all image details or just summaries.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention any exclusions, prerequisites, or specific use cases. It simply restates the function, leaving the agent to infer usage from the name. No alternatives are noted, unlike tools that explicitly recommend sibling tools.

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