transport_status

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

The description clearly indicates a read-only query with no side effects, listing the exact state variables. Without annotations, it effectively communicates the tool's behavior. Minor omission on potential failure conditions, but adequate for a simple getter.

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?

Extremely concise: one sentence listing key fields with no filler. 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?

Given low complexity and no output schema, the description adequately specifies what is retrieved. Could include format details (e.g., position in beats or time) but not strictly necessary for an agent familiar with the domain.

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?

No parameters exist (empty input schema), so the baseline of 4 applies. The description adds no parameter information, which is acceptable as 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 description explicitly states it retrieves specific transport state fields (is_playing, is_recording, position, loop mode, tempo, signature), clearly distinguishing it from sibling tools like transport_play or transport_set_tempo.

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 on when to use this tool versus alternatives such as transport_set_tempo for setting values; the description solely lists returned fields without context.

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