Read the timecode pool or one timecode show

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

With no annotations, the description carries the full burden and does so well: it declares read-only, states that armed state and external reception are not readable, asserts these tools never record, and names the required bridge version. It omits error behavior and any size/pagination traits, keeping it from a 5.

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 front-loaded and wastes few words, but the bulk arrives as one enormous run-on sentence packed with parentheticals that is hard to parse. A short bulleted breakdown of returned fields would read much better.

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 complex read tool with no output schema and no annotations, the description does the heavy lifting by enumerating the returned fields (source, playback/recording settings, track groups, events, raw time, actions) and the version prerequisite. Only failure/pagination behavior is left unaddressed.

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 0%, so the description must compensate, and it largely does: timecode selects one show, slots:true lists the 16 slots, and fps governs the H:MM:SS:FF format at 24/25/30/60. The numeric type of timecode and its value domain remain only loosely implied.

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 gives a specific verb (read) and resource (timecode pool or one timecode show), and the two operating modes are unambiguous. It is clearly a read tool distinct from the build/transport siblings, though it never names those alternatives explicitly.

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?

'Without timecode: the timecode pool. With timecode: ...' gives a clear condition for selecting each mode, plus the useful caveat that slots:true lists the 16 slots. It stops short of routing the agent away from gma3_build_timecode or gma3_timecode_transport, so no explicit alternatives are offered.

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