hcloud_list_rds_instances

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds no behavioral detail of its own, such as pagination or how far a listing spans, but it also contradicts nothing.

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?

A single front-loaded sentence with zero waste, but its brevity reflects under-specification rather than economy. There is nothing structurally wrong, just nothing helpful.

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?

With no output schema and a large family of near-identical list tools, the description should at least state what an instance record contains or how listing scope works. As written, an agent can do little more than call it blindly with a region.

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 baseline is 3. Both parameters ('region', 'limit') are documented in the schema, though thinly; the description adds no meaning about region scope or default page size.

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 decodes the tool name and nothing more: 'List RDS database instances' restates hcloud_list_rds_instances verbatim. It never distinguishes RDS instances from the many sibling instance-list tools (gaussdb, dds, dcs, sms), so an agent gets no identification value beyond the name itself.

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 prerequisite (e.g. region is required), and no alternative named. The agent must infer everything from the schema's required field.

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