vast42_list_icons

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'List all VAST 4.2 icons', which implies read-only behavior but does not explicitly state side effects, pagination, or required permissions. The default limit of 100 is not mentioned, potentially misleading the 'all' claim.

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?

Single sentence with no wasted words. It is appropriately brief for a list operation.

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?

The description is minimal but generally sufficient for a simple list tool. However, it omits pagination details and the fact that 'all' is limited by default, which could lead to incomplete retrieval expectations.

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 input schema already fully documents both limit and offset parameters with descriptions. The description adds no additional parameter semantics, but baseline of 3 applies due to high schema coverage.

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 identifies a list operation for VAST 4.2 icons, using the verb 'List' and a specific resource. It distinguishes from sibling get/create/update/delete icon tools by indicating the plural 'all icons'.

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?

No guidance is provided on when to use this tool versus alternatives like vast42_get_icon or vast42_list_icon_click_fallback_images. There is no mention of use cases or exclusions.

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