get_all_tracks_info

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states that it returns a list of tracks with specific fields, which is useful. However, it does not explicitly mention that this is a non-mutating read operation, nor does it address potential side effects, performance implications, or error behavior. For a 'get' tool, the risk is lower, but transparency is still partial.

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 only two sentences. The first sentence states the purpose, and the second lists the return fields and the use case. Every word earns its place; there is no redundancy or fluff.

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 parameterless read-only getter, this description is complete. It specifies what it does, what data it returns, and when it is useful. The existence of an output schema further reduces the need to describe the return structure. No critical information is missing for an agent to select and invoke this tool 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 takes zero parameters, and the description correctly does not attempt to explain any. With no parameters, the baseline of 4 applies. The description adds no parameter semantics because none are needed; the schema already trivially covers all (non-existent) parameters.

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 states the exact action ('Get summary information') and targets 'all tracks at once', clearly distinguishing it from the sibling get_track_info which handles individual tracks. The list of returned fields (name, type, color, mute, solo, arm, etc.) further clarifies the scope and purpose.

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 description provides clear usage context: 'Useful for getting a full session overview without making separate calls per track.' This implies when to use it (full overview) and contrasts with per-track calls. However, it does not explicitly name an alternative tool or state when not to use it, so it misses the full 'when/when-not' guidance.

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