list_image_management

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

No annotations are provided, so the description carries the burden. It discloses that the tool lists three kinds of resources, but it doesn't describe any behavioral traits like pagination, filtering, or whether it returns all items at once. For a read-only list operation, the lack of annotations is partially mitigated by the simple scope, but more behavioral context (e.g., pagination, result limits) would be valuable.

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 sentence that is concise and front-loaded with the action and resource. It wastes no words, though it could be slightly more informative about behavior. The trailing whitespace is a minor formatting issue but doesn't affect clarity.

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?

For a simple list tool with one parameter and an output schema, the description is mostly complete. However, it doesn't mention any pagination, filtering, or result size limits, which are common for list operations. The output schema exists, so return values are covered, but behavioral context is thin.

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%, and the schema already documents the 'resource' parameter with an enum and descriptions for each value. The description adds minimal value beyond the schema, essentially restating the enum values. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('List') and resource ('image management streams, versions, or tags'), which clearly distinguishes it from sibling tools like list_connection_servers or list_desktop_pools. It doesn't explicitly name a sibling alternative, but the resource scope is clear enough to differentiate it from other list tools.

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 implies usage by listing the three resource types, but it doesn't explicitly state when to use this tool versus alternatives. There are no exclusions or alternative tool references. The context is clear for a simple list operation, but no explicit guidance is provided.

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