transport_record

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

The description implies a state change (starts recording) but lacks details on prerequisites (e.g., armed tracks), side effects (e.g., overwriting existing recordings), or post-conditions. No annotations are present to supplement.

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?

At two words, the description is extremely concise but at the expense of clarity and completeness. It omits essential context, making it under-specified rather than efficiently 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?

Given the simplicity of the tool (no parameters, no output schema), a minimal description might suffice, but the lack of prerequisites, effects on transport state, and relationship to other transport tools makes it incomplete. An agent would need additional context to use it correctly.

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 no parameters, and the schema coverage is 100%. The description adds no parameter information, which is acceptable as there are none to document.

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 'Start recording.' clearly indicates the tool initiates a recording process, which is a specific verb and activity. However, it does not specify what exactly is being recorded (e.g., audio on selected tracks) and does not distinguish it from sibling tools like transport_play or transport_stop.

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 guidance is provided on when to use this tool versus alternatives. Sibling tools include transport_play, transport_stop, and others, but the description offers no context for selection.

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