refresh_gcp_pricing

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

Annotations already mark the tool as readOnlyHint, idempotentHint, and not destructive. The description adds that the data comes from a specific external source (instances.vantage.sh) and provides the scope (287 types, 40+ regions). It doesn't contradict annotations and adds useful behavioral context beyond the annotations.

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 two sentences, front-loaded with the action and source, and provides key details about the output. Every sentence adds value with no redundant or filler 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?

The tool is a simple read-only data fetch with no output schema. The description explains the source, coverage, and number of instance types. It could mention that the results may include a large dataset or note the default maxResults, but the schema covers that. It is largely complete for the 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?

Schema description coverage is 100%, with each parameter already having a clear description in the input schema. The tool description does not add extra meaning beyond what the schema provides, so it does not compensate beyond the baseline. The schema itself is clear enough.

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 states the tool fetches real-time GCP Compute Engine pricing from instances.vantage.sh and returns 287 instance types with on-demand and spot pricing across 40+ regions. This is a specific verb+resource combination that distinguishes it from sibling tools like refresh_aws_ec2_pricing.

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 versus alternatives. It does not mention prerequisites, exclusions, or when not to use it. For example, it doesn't suggest this tool for general GCP pricing queries versus other refresh tools for different providers.

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