Tv State Watch

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

With no annotations, the description carries the full burden and does useful work: it discloses the non-obvious streaming behavior (count progress notifications at interval spacing, final snapshot returned last), which an agent could not guess from the schema. It omits error/cancellation behavior and any permission requirements.

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 short lines, front-loaded with the core action and mechanism, with no filler. Every sentence adds information.

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 no explanation, and the streaming semantics and defaults are covered. For a no-annotation streaming tool it is nearly complete, though it lacks any note on interruption/auth behavior.

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 baseline is 3, but the description adds real meaning by explaining how count and interval compose into the default watch duration (12 x 5s = 1 minute). That relationship is not derivable from the individual parameter descriptions alone.

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?

Names a specific verb (stream/watch) plus resource (tv_state snapshots) and the delivery mechanism (progress notifications), which cleanly separates it from the sibling tv_state single-snapshot tool. It stops short of explicitly naming tv_state as the alternative, so sibling differentiation is implied rather than stated.

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?

The 'Default is 1 minute of watching' line implies this is for time-boxed observation, but there is no explicit when-to-use vs. tv_state or tv_status, no conditions, and no exclusions. Usage must be inferred from the streaming mechanics.

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