tracking-track_report

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It implies a read-only report operation, but it does not explain what the returned report contains, whether the clip must be loaded, or what kinds of tracks are included.

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 short sentence with no filler, front-loaded with the action 'Report tracks' and immediately scoped to 'a clip'. Every word earns its place.

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 tool with no output schema, no annotations, and a single but undocumented parameter, the six-word description is too sparse to give an agent enough confidence about expected result and behavior. It is minimally usable but leaves important gaps.

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%, and the description is not compensated for explaining the parameter. It only restates the clip concept already represented in the schema; it does not describe how to format the clip name or how the clip parameter relates to track reporting.

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 uses a specific verb+resource ('Report tracks') and scopes it to a clip, which distinguishes it from sibling tools like tracking-report or tracking-marker_report. The word 'report' is somewhat generic, but the clip scoping makes the intended purpose reasonably clear.

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 phrase 'for a clip' implies this tool is for per-clip track reporting rather than general tracking reporting, but it does not explicitly state when to choose it over siblings or name any alternatives. Usage context is embedded but not directly detailed.

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