describe_vpcs

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

Annotations indicate readOnlyHint=true, which aligns with 'Query.' The description adds default values for page_number and page_size, and notes that vpc_id can accept up to 20 IDs separated by commas, which is behavioral context beyond the schema.

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 front-loaded with the purpose and then lists parameters in a structured docstring format. It is slightly verbose but clear and well-organized, earning its place.

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 output schema exists, the return value description ('Dict[str, Any]') is sufficient. All parameters are covered, pagination is explained, and the tool is a simple read-only list query. No gaps detected.

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 coverage is 0%, so the description carries the full burden. It provides meaningful descriptions for all 8 parameters, including defaults and constraints (e.g., 'Up to 20 VPC IDs,' 'Maximum value: 50' for page_size), significantly aiding parameter understanding.

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 starts with 'Query VPC list,' clearly indicating the verb and resource. The parameter list details specific filters (region_id, vpc_id, etc.), distinguishing it from sibling tools like describe_vswitches, which are about subnets, not VPCs.

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 vs alternatives. There is no mention of alternative tools like describe_vswitches or when to use this instead of other listing tools. The description only explains parameters.

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