sdcloud_sync_mnha_cluster

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

With no annotations, the description carries the full burden of transparency. It discloses that the operation is asynchronous by stating it returns a job id and directs polling for progress. However, it does not mention any potential side effects, permissions, or whether multiple syncs can be triggered concurrently.

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 two sentences, each purposeful. The first identifies the action and resource, the second provides the follow-up polling instruction. No redundant or unnecessary words.

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?

The description adequately covers the core purpose and async nature for a straightforward sync trigger. However, it lacks details on prerequisites, error handling, and the structure of the body parameter, which, combined with no output schema, leaves some gaps for the agent.

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?

The description adds no information about the parameters beyond what the input schema provides. One parameter (mnha_cluster_id) has no description in either the schema or the tool description, and the body parameter's schema description is generic. With 50% schema coverage, the description should have compensated but did not.

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 the action ('Trigger a sync') and the resource ('MNHA cluster'), with the acronym expanded. It distinguishes itself from sibling tools like sdcloud_sync_devices by naming the specific cluster type.

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?

The description provides a clear context for when to use the tool (to sync an MNHA cluster) and instructs the user to poll sdcloud_get_mnha_cluster_sync_status for progress. However, it does not mention any alternatives or conditions when this tool should not be used, which is a gap given the number of sibling sync tools.

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