create_vast_custom_report

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

No annotations are provided, and the description offers no insight into what a VAST report configuration is, whether it is persisted, what response to expect, or any side effects. The sentence is purely a statement of the 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?

The description is a single, concise sentence that directly states the operation. It is appropriately short with no unnecessary wording.

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 large number of report-related sibling tools (create_custom_report, create_report_schedule, update_custom_report, etc.), the description lacks context on what a VAST report configuration specifically involves, or how it relates to other report tools. No output schema exists, so the description should explain the outcome or return value, but it doesn't.

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 the 'name' parameter with type string and description 'Report name'. The description does not add any additional semantics about how 'name' is used or what constitutes a valid configuration.

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 uses the verb 'Create' with the resource 'VAST report configuration', clearly indicating the action. It does not explicitly distinguish from the sibling 'create_custom_report', but the 'VAST' qualifier gives some specificity.

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?

There is no mention of when to use this tool or alternatives. No exclusions, prerequisites, or guidance on selecting between create_vast_custom_report, create_custom_report, and create_report_schedule.

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