Move a filter

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the bar is lower; the description still adds real context the annotations lack — dry_run defaults to true (describe-only), the live-streaming guard, and that the before/after order is reported. It does not spell out what happens to existing ordering or permissions required.

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?

Three tight sentences: what it does, what it returns, and the safety guard — each front-loaded and free of 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 5-parameter mutation tool with no output schema, the description covers the guard semantics and the return ('shows the order before and after'), which substitutes for an output schema. Minor gaps are the two string parameters and the reorder's effect on existing indices.

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 40% schema coverage, the description must compensate and does so for the key ambiguous parameter: 'filterIndex (0 = top, applied first)' gives positional meaning the schema's bare minimum:0 does not. sourceName and filterName remain undocumented anywhere, but their intent is largely inferable from the name.

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 (moves) and resource (a filter) plus the position semantics ('0 = top, applied first'), which cleanly separates it from siblings set_filter_settings and set_filter_enabled that alter a filter's configuration or state rather than its order.

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 clear precondition for the risky case ('needs confirmLive=true while streaming/recording') and warns to ask the person first, but never names the alternative tools or when a caller should prefer set_filter_settings over reordering.

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