Read the video path

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds the shape and units of the returned data (cm, degrees, m/s), which is useful context, but it does not disclose any behavioral traits beyond the output format already likely captured by the 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, front-loaded fragment naming the resource and its data structure, followed by one short sentence directing mutations elsewhere. Every phrase earns its place 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 zero-parameter read tool with annotations covering safety and an output schema managing return values, the description supplies the key data shape, units, and the alternative for mutation. Nothing needed to call the tool correctly is missing.

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?

The tool has zero parameters, so the baseline is 4. The description provides no parameter details, which is appropriate since there are none.

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 title states the verb 'Read' and the resource 'video path,' while the description names the specific data returned (camera path with fps, speed, secs, rows, units). It distinguishes from the sibling edit_video by stating that changing and rendering use edit_video. The description alone lacks an explicit verb, but the combined definition is 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 'Change it and render it with edit_video' explicitly routes mutation and rendering to the sibling tool, implying this tool is for reading the current path. It provides a clear alternative and context, though it doesn't spell out when to read (e.g., before or after edits).

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