tv_scroll

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

With no annotations, the description carries the full disclosure burden. 'Bounded scrolling' and 'automatic unknown-app fallback' hint at clamping and a fallback path, but neither is explained, and nothing is said about permissions, side effects, or state changes beyond the vague phrase 'lightweight state.'

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?

It is a single short sentence with no padding, so it is structurally tight. However, the brevity comes at the cost of under-specification rather than achieved conciseness.

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?

An output schema exists so return values need not be described, but with two undocumented parameters (0% coverage), no annotations, and only vague behavioral hints, the definition is not complete enough for an agent to invoke the tool confidently.

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 0% for both parameters, so the description must compensate and it does not. Neither 'dy' (direction/amount?) nor the 'capture' enum (auto/never/always) is mentioned, leaving their meaning and accepted values entirely to inference.

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 names the resource (scrolling) but the verb is only implied and the modifier 'bounded' is ambiguous. It does not distinguish tv_scroll from siblings like tv_move, tv_press, or tv_click, and never states that this scrolls a TV UI surface.

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?

There is no when-to-use or when-not-to-use guidance and no reference to any alternative tool. The only contextual hint is 'automatic unknown-app fallback,' which is a behavior, not a selection rule.

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