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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety framing is partly covered; the description still adds real value by disclosing the URL change side effect and the uniqueness precondition. It omits mutation-specific context the annotations don't cover, such as required permissions on both namespaces, whether the move is reversible, and whether old links redirect or break.

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?

Four short sentences, each carrying distinct information: action and scope, uniqueness precondition, side effect, and intended use case. No filler and the action is front-loaded.

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 two-parameter mutation with no output schema, the description covers purpose, precondition, and post-move side effect adequately. Gaps remain around authorization requirements and whether the move can be undone, which matter for a namespace-transfer operation.

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%, and the schema itself documents both board_id and namespace_slug including the list_namespaces discovery hint, so the baseline is 3. The description's remark about the 3-character code being unique in the target namespace adds useful constraint context for namespace_slug but no format or semantics beyond the schema.

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 specific verb and resource plus the source/target scope ('from its current namespace to a target namespace'), which is far more precise than 'Move board' alone. It does not explicitly differentiate itself from close siblings like transfer_board_ownership, bind_board_to_group, or update_board, so an agent must infer the distinction.

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 a concrete use case ('consolidate boards into an organization namespace') and an important precondition (code must be unique in the target namespace), which tells the agent when the call is appropriate. It stops short of naming alternatives or exclusions, e.g. when to use transfer_board_ownership instead.

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