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

The annotations already disclose readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output behavior (frame count and elapsed seconds) and mentions drop-frame support, but it does not describe edge cases, error handling, or the exact return structure, which are relevant since there is no output schema.

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, tightly worded sentence that leads with the core parsing behavior, states the outputs, and then introduces the optional conversion. Every clause carries information with no filler.

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 moderately complex calculator without an output schema, the description names the main outputs and the optional conversion target. The schema fully covers parameter semantics, including drop-frame notation and mode behavior. It falls slightly short only by not giving an example or explaining invalid-input 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 description coverage is 100%, and the schema provides detailed descriptions for timecode, rate, to_rate, and mode, including enum values and the semantic difference between 'time' and 'frames'. The description itself adds little parameter-level meaning beyond framing the tool as a timecode calculator.

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 a specific action (parse SMPTE timecode at a given frame rate) and explicit outputs (frame count, real elapsed seconds), plus an optional conversion behavior. This distinguishes it from sibling tools like convert_file and inspect_file, whose domains are file operations rather than timecode math.

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 explicit guidance is given about when to choose this tool over alternatives, nor are there exclusion conditions. The intended usage is only implied by the domain of the description; the siblings are not referenced or differentiated.

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