dynadot_set_folder

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

No annotations exist; the description lacks behavioral details such as whether the move is destructive (removes from old folder), any side effects, or authorization requirements. The simple verb 'move' leaves ambiguity.

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 sentence, but it omits necessary details. Conciseness should not come at the cost of completeness; a slightly longer description would be more 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?

Given no output schema, no annotations, and three parameters, the description fails to explain return values, prerequisites, or the full meaning of 'move.' This leaves the agent uncertain about the tool's behavior.

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 coverage is 67% (folder and folderId have descriptions). The description adds no extra meaning beyond the schema, only restating the action. The baseline of 3 is appropriate since schema does most of the work.

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 'Move a domain to a folder.' uses a specific verb (move) and resource (domain to folder), clearly distinguishing it from siblings like dynadot_create_folder or dynadot_set_folder_dns.

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?

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites (e.g., folder must exist) or whether the move is additive or replaces current folder membership.

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