dataverse_list_plugin_step_images

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds context that images are pre/post snapshots, but no additional behavioral traits such as pagination limits (handled by schema) or authentication needs. With strong annotation coverage, description adds moderate value.

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, front-loaded with the primary purpose. No redundant words. Efficiently communicates the core functionality.

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 tool is a list operation with an output schema, the description is minimal but sufficient. It does not explain return values (handled by output schema) or mention that it is a read operation (annotations cover it). Could be improved by noting that step_id is optional and what happens when omitted.

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 high (all parameters described). The tool description only reiterates step_id usage, which is already in the schema. Adds no new parameter meaning beyond what the schema provides.

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 states the tool lists plug-in step images, explaining they are pre/post entity snapshots. The name and description effectively distinguish it from sibling tools like dataverse_get_plugin_step_image (singular retrieval) and dataverse_list_plugin_steps (lists steps, not images).

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 provides a guideline for using step_id to scope to one step, but does not explain when to use this tool versus alternatives like dataverse_get_plugin_step_image for a single image or dataverse_list_plugin_steps for steps. Lacks when-not guidance.

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