list_distributions

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

With no annotations, the description partially discloses behavior: it lists cells and includes flags for VoseInput/VoseOutput. However, it does not mention performance implications, required permissions, or side effects, leaving gaps in transparency for a potentially large list operation.

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 tightly written sentences. The first sentence states the core purpose; the second adds the optional filter. No wasted words, and the key information is front-loaded.

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 parameter set (2 params, 1 required) and the presence of an output schema, the description adequately covers what an agent needs to know. It specifies the scope and optionality, making it complete for this tool's complexity.

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 description explains the 'sheet' parameter ('restricts the scan to one sheet'), adding meaning beyond the schema. However, it does not describe the required 'workbook_name' parameter, and schema coverage is 0%, so the description only partially compensates.

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 specifies the action: 'list every cell containing a Vose distribution / aggregate / copula / time-series / fitting function'. It names the resource (cells with specific functions) and distinguishes from siblings like list_modelrisk_inputs/outputs which focus on specific wrapped cells.

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 states the purpose but does not explicitly say when to use this tool versus alternatives (e.g., list_modelrisk_inputs). It mentions an optional sheet filter, which provides some context, but lacks guidance on exclusions or prerequisites.

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