storage_container_list

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

With no annotations, the description carries full burden. It indicates a read operation with '[READ]' and describes the limit parameter's effect, but does not explicitly confirm idempotency, lack of side effects, or authentication requirements. The disclosure is adequate but not comprehensive.

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 brief and front-loaded with the core purpose. The Args block uses a clean format. It could be slightly more structured (e.g., separating purpose and parameters), but it is efficient without waste.

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 no output schema, the description lists returned fields and explains limit reporting. It is complete for a simple list tool, though it omits pagination details beyond the truncated flag and error handling. Overall, sufficient for correct invocation.

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 0%, so the description must fully explain parameters. It clearly defines 'limit' (max rows, default 500, with truncation reporting) and 'target' (Prism Central name, omit for default). This adds essential meaning beyond the schema's bare property definitions.

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 starts with '[READ]' and explicitly states 'List storage containers' along with the fields returned (extId, name, cluster, capacity, usage, RF). It clearly distinguishes this tool from sibling list tools (e.g., snapshot_list, host_list) by its resource type.

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 explains the limit and target parameters, including default behavior and the report of truncated results. However, it does not explicitly state when to use this tool versus other list tools or provide exclusions (e.g., when to use storage_container_list vs storage_container_get or alternative filtering methods).

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