conduyt_move_smart_view

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

With no annotations, the description carries the behavioral burden and discloses that this is a mutation requiring an admin key, that exactly one anchor is required, and that other views retain relative order. It also explains the Smart Dialing priority effect, though it does not describe failure modes or the response.

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 dense and front-loaded: action, anchor semantics, positional invariant, size-limit differentiation, and priority meaning all appear without filler.

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 mutation tool with no annotations and no output schema, the description covers auth requirements, positional behavior, the alternative tool, and the dialing-priority consequence. It stops short of describing error conditions or return behavior, leaving a minor gap.

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 100%, so the schema already defines id, beforeId, and afterId thoroughly. The description reinforces that exactly one anchor is required, but adds little beyond the existing parameter descriptions, so the baseline of 3 is appropriate.

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 states a specific verb and resource: moving one Smart View within sidebar order. It also distinguishes this tool from the capped bulk reorder sibling by calling out the >200 views use case.

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?

It gives explicit invocation rules: pass the moved view's id plus exactly one anchor, beforeId or afterId. It names the alternative conduyt_reorder_smart_views and explains the cap condition that selects this tool instead.

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