Export Visual Trajectories

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which describe the safety profile. The description adds no extra behavioral context (e.g., output delivery, rate limits, or side effects). It does not contradict annotations, but also does not enrich them.

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 sentence that directly states the tool's purpose. There is no wasted wording or redundancy, making it highly concise.

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 an export tool with no output schema, the description does not clarify what the exported data looks like or how it will be delivered (e.g., a file path, download URL, or inline payload). It provides adequate context for the tool's purpose but lacks important details about the export result.

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%, with all three parameters having descriptions in the schema itself. The description adds no additional meaning beyond what the schema already provides. The enum for 'format' is well-defined in the schema.

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 specifies a clear verb ('Export'), a concrete resource ('multimodal visual state transition trajectories'), and the intended purpose ('for local model fine-tuning'). This distinguishes it from sibling tools like export_joint_trajectories, which likely exports a different type of trajectory data.

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 local model fine-tuning' implies the primary use case, but there is no explicit guidance on when to use this tool versus alternatives such as export_joint_trajectories or export_snapshot. No exclusions or alternative tools are mentioned.

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