transport_status

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

With no annotations, the description carries the burden of disclosing behavior. 'Get' strongly implies a read-only operation with no side effects, and the field list clarifies what is returned. However, it does not describe return format, units, or behavior under edge conditions like an unconnected bridge or stopped transport.

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?

A single front-loaded sentence with no wasted words. Every listed field is meaningful and directly relevant to the tool's purpose.

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-only status tool, the description is largely complete: it names the resource and all returned fields. It could be slightly improved by indicating return value types or units, but nothing essential is missing for an agent to invoke 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 zero parameters and schema coverage is 100%, so the baseline is 4. The description adds value beyond the empty schema by enumerating the output fields an agent can expect, making the return payload predictable.

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 ('Get') and resource (transport status) and enumerates the exact fields returned: is_playing, is_recording, position, loop mode, tempo, signature. This clearly separates it from mutating transport tools like transport_play or transport_stop, though it does not explicitly differentiate it from other status-style tools such as live_status.

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 about when to use this tool versus alternatives. The field list implies it is for reading current transport state, but there is no explicit statement of context, exclusions, or comparison to related tools like arrangement_play_time or transport_song_length.

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