hcloud_list_route_tables

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on pagination via limit, no mention of what the VPC filter does, and no hint about result scope or ordering.

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?

Three words with no wasted clauses, but also no front-loading of anything useful because there is essentially no content. Conciseness here is under-specification rather than disciplined editing.

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?

For a list tool with a required region, a VPC filter and a limit, in a catalogue with dozens of overlapping list tools including hcloud_list_er_route_tables, the description does not do enough to disambiguate or explain the call. Only the annotations and schema carry the definition.

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%, so the three parameters are documented in the schema itself and the baseline is 3. The description adds no extra meaning, syntax or defaults beyond those terse schema strings ("Region", "Max results", "Filter by VPC ID").

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?

"List route tables" restates the tool name (hcloud_list_route_tables) almost word for word, adding no scope, no resource qualifier and no distinction from near-neighbours such as hcloud_list_er_route_tables. An agent can infer only that it is a list operation on some route-table resource.

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 when-to-use guidance, no mention of prerequisites (region is required), and no pointer to alternatives such as hcloud_list_er_route_tables or hcloud_list_vpcs. Nothing tells the agent how to choose between these listing tools.

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