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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false; the description reinforces this with 'opens nothing by itself', which removes any doubt that the tool is advisory-only. It also discloses the absence of a public Gymdesk API, explaining why the browser-based follow-up is necessary. It does not describe output structure or length of the returned guide.

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?

Purpose and the key non-execution caveat are front-loaded in the first two sentences, and the API note justifies the browser hand-off. The closing API sentence is somewhat bloated, listing three 404 URLs and an oddly specific date, which is more provenance than an agent needs.

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 parameters and no output schema, the description carries the burden and does so for the mechanics: what it returns, that it performs nothing, and what to use next. The remaining gap is scope — it never says which categories of settings can be migrated between locations, leaving an agent unsure whether a given setting is covered.

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 tool takes zero parameters, so the baseline is 4; there is no argument meaning to add or omit. The description correctly implies no inputs by framing the tool as a pure instruction generator.

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?

States a concrete verb and resource (migrate settings between locations) and immediately qualifies the deliverable: it returns step-by-step instructions rather than performing the migration. An agent can distinguish it from the many sibling 'configure_*' tools because it is a guidance tool, though it never names a sibling explicitly.

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?

Gives clear operating context: this tool yields the how-to, and the actual work is then done with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. That is an explicit hand-off instruction. It stops short of stating when-not to use it (e.g. if the locations are already identical or the user wants a direct API path).

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