hcloud_list_organizations_accounts

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so safety is covered. The description adds nothing beyond that — no note on pagination, whether results are scoped to the caller's organization, or how region affects the result set.

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 single phrase is free of waste but is under-specified rather than concise; there is no front-loaded statement of scope or behavior to anchor the call. It reads as a label, not a definition.

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 two-parameter, no-output-schema list tool with annotations covering safety, the definition still leaves the core question unanswered: what an "account" is in this Organizations hierarchy and how region and parent_id constrain results. That is a material gap for correct invocation.

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 only two parameters (region required, parent_id optional), so the schema carries the burden and the baseline of 3 applies. The description does not clarify that parent_id is an OU filter or what a valid region value looks like.

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 Organizations accounts" essentially restates the tool name hcloud_list_organizations_accounts with the prefix stripped; it adds no scope, filter, or return-shape detail. It does not distinguish this tool from the adjacent hcloud_list_organizations_ous sibling beyond the trailing noun.

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 statement of prerequisites or required permissions, and no mention of alternatives such as listing OUs first to obtain a parent_id. The agent must infer usage entirely from the name.

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