get_vast_geo_summary_report

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It reveals only that the operation is a 'Get' (read), but says nothing about what the geographic summary contains, how data is aggregated, whether filters are required, or what the response looks like. This is minimal disclosure.

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 succinct sentence with no redundant words. It is appropriately concise for a getter tool, though it lacks any additional structural elements like sections or examples. It earns its place as a clear purpose statement.

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 tool has 6 optional parameters, no output schema, and no annotations, yet the description provides only a bare phrase. It does not explain what a 'geographic summary report' is, how it relates to other VAST reports, or how the filters affect the output. This is insufficient context for correct 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 100% for all 6 parameters, so the baseline is 3. The description itself adds no parameter semantics, but the schema already provides clear descriptions for each filter (e.g., 'Filter by zone IDs'). The description does not need to repeat this.

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 'Get VAST geographic summary report' clearly states the action (Get) and the specific resource (VAST geographic summary report), distinguishing it from sibling tools like get_geo_summary_report and get_vast_report. The verb and resource are unambiguous.

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 provides no guidance on when to use this tool vs. alternatives such as get_geo_summary_report or get_vast_report. There is no mention of when to choose this over others, no prerequisites, and no exclusions.

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