list_vast_custom_reports

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

With no annotations, the description must disclose behavior on its own, but it only says 'List all VAST report data'. It does not mention that this is a read-only operation, whether pagination is applied (though limit/offset exist), what the response contains, or any filtering or side effects.

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 extremely brief, containing no wasted words, but it is under-specified to the point of being vague. Like the 'Process' example, this is not conciseness but insufficient content.

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 absence of annotations and output schema, and the proliferation of similar report-related sibling tools (e.g., list_custom_reports, get_vast_custom_report, list_all_generated_reports), this description is wholly inadequate. It fails to clarify what 'VAST report data' means, what the tool returns, or how it differs from its siblings.

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 fully documents both parameters (limit and offset) with descriptions, covering 100% of schema properties. The description itself adds no extra parameter context, but the high schema coverage sets a baseline of 3.

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 says 'List all VAST report data' but does not clearly specify what is being listed—custom report definitions or the data within reports. The tool name 'list_vast_custom_reports' implies listing custom reports, but the description's noun phrase is ambiguous and does not distinguish this from the sibling 'list_custom_reports'.

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 instead of alternatives like 'list_custom_reports', 'get_vast_custom_report', or other report-related tools. The description lacks any context about 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.