hcloud_list_sms_migration_projects

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds no behavioral context beyond the title, such as whether results are paginated automatically, whether all projects are returned, or what region scoping means. It does not contradict the annotations, but it contributes essentially no behavioral detail.

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 front-loaded sentence with no wasted words. It expands the SMS acronym, which adds useful disambiguation without verbosity. There is no clutter or repetition.

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 simple list tool with full schema coverage and explicit read-only annotations, the description is minimally sufficient to identify the operation. However, it lacks usage context and does not explain return behavior, and there is no output schema to fill that gap. It is adequate but thin for an agent choosing among many sibling list tools.

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 parameters limit, offset, and region are already documented in the input schema. The description adds no additional meaning about required region behavior or pagination semantics. Baseline 3 is appropriate because the schema carries the parameter documentation.

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 clearly states a specific verb and resource: list SMS (Server Migration Service) migration projects. The SMS expansion disambiguates it from generic project-listing siblings such as hcloud_list_projects. It does not explicitly contrast with sibling SMS tools like hcloud_list_sms_servers or hcloud_list_sms_tasks, but the resource is distinct enough.

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 exclusions, and no suggested alternatives. An agent must infer from the name that this is the tool for listing SMS migration projects rather than SMS servers or tasks. No prerequisites or contextual constraints are stated.

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