obs-get-source-filter-list

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

No annotations are provided, so the description carries full burden. It states the action ('Gets') but doesn't disclose behavioral traits such as whether this is a read-only operation, potential errors (e.g., invalid source name), or the return format (e.g., array structure). This leaves gaps for safe and effective use.

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, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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 read operation with one parameter and no output schema, the description is minimally adequate. However, it lacks details on return values (e.g., array format) and error handling, which could be important for integration. Without annotations, it doesn't fully cover behavioral aspects needed for robust use.

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%, with the single parameter 'sourceName' documented as 'Name of the source'. The description adds no additional meaning beyond this, such as examples or constraints on valid source names. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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 ('Gets') and resource ('array of all of a source's filters'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'obs-get-source-filter' (singular) or 'obs-get-filter-kind-list', which could cause confusion about scope.

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. Given siblings like 'obs-get-source-filter' (singular) and 'obs-get-filter-kind-list', the description lacks context about selecting this tool for retrieving all filters of a specific source rather than individual filters or filter types.

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