sd_move_nodes

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

Annotations indicate idempotentHint=true, so the tool is safe to repeat. The description adds constraints: moves up to 100 explicitly identified nodes to finite coordinates, which goes beyond annotations. However, it omits details like error handling or coordinate restrictions.

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 that is front-loaded and contains no extraneous words. Every phrase adds value.

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 the tool's complexity (2 required parameters with nested objects) and the existence of an output schema, the description is minimal but functional. It lacks information about permissions, failure modes, or response structure, but the idempotent hint covers safety.

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?

With 0% schema description coverage, the description should compensate more. It mentions 'explicitly identified nodes' (node_identifier) and 'finite coordinates' (position array of 2 numbers) but does not explain the graph parameter or the structure of moves. Leaves much to inference.

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 verb 'Move' and the resource 'nodes', with explicit constraints of 1-100 nodes and to finite coordinates. It distinguishes from sibling tools like sd_create_node (creates) and sd_delete_nodes (deletes) by specifying movement.

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 implies when to use (to reposition nodes) but provides no explicit when-not or alternatives. Sibling tools such as sd_set_node_parameter could be used for other property changes, but no guidance is given.

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