Set Source Filter Index

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

The description adds no behavioral context beyond the annotations. It doesn't disclose that the filterIndex must be within the current number of filters, nor any side effects on filter ordering. Annotations already declare idempotentHint=true, but the description contributes no additional insight.

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?

A single sentence with no filler, front-loading the action and resource. This is perfectly sized for the tool's simplicity.

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 simple setter with complete schema and annotations, the description is minimally adequate. However, it lacks guidance on valid index ranges, the optional canvasUuid parameter, and how this tool fits into filter management. It meets the minimum viable bar but leaves clear gaps.

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?

The input schema covers all four parameters with descriptions (100% coverage), so the description doesn't need to add parameter details. It only restates that filterIndex is the 'new index position,' which adds no extra meaning 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?

The description uses the specific verb 'Sets' and clearly identifies the resource: 'the index position of a filter on a source.' This distinguishes it from sibling filter tools like obs-set-source-filter-settings or obs-set-source-filter-enabled, which focus on other attributes.

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. It doesn't mention that this tool reorders filters, requires an existing filter, or suggest how to discover valid indices. The description simply states the action without context.

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