list_vpc_route_tables

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

Annotations are absent, so the description must disclose behavior. It only states the action and scope; it does not mention read-only nature, behavior when folder_id is omitted, pagination, or required permissions. This is a significant gap given no 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 a single focused sentence with no extraneous content. It fronts the verb and resource directly, making it appropriately concise.

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?

While the tool is simple, the description omits what happens when folder_id is not provided (since it's optional) and offers no context about the returned list or any side effects. Given no annotations or output schema, the description is not complete enough.

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 0%; the description only references 'specified folder' without explaining the folder_id parameter, its optionality, or default behavior. It adds little beyond the field name, so it cannot compensate for the lack of schema descriptions.

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?

Description explicitly states the action ('List'), resource ('route tables'), and scope ('in specified folder'). This clearly distinguishes it from sibling tools for other VPC resources, earning a full score.

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 information is provided about when to use this tool versus other list tools, nor any prerequisites or exclusions. The context is purely declarative, so the agent receives no guidance on selecting this tool.

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