list_modelrisk_inputs

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

No annotations; description is the sole source. It states the tool returns specified info but omits side effects, authorization, or performance implications. Basic transparency but not thorough.

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 key action upfront and return details. Efficient but could benefit from structured bullet points for readability.

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 a single parameter and output schema likely defined elsewhere, the description covers the core functionality. Lacks edge cases (e.g., empty result) but is sufficient for typical use.

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%, yet the description adds no additional context for the workbook_name parameter (e.g., format, validity constraints). Fails to compensate for missing schema descriptions.

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?

Description clearly states it lists cells wrapped with VoseInput() and enumerates returned fields (reference, name, formula, value). This distinguishes it from siblings like list_modelrisk_outputs.

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?

Description implies usage (to find VoseInput cells) but provides no guidance on when to choose this tool over alternatives like discover_inputs or list_modelrisk_outputs.

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