track_select

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

No annotations are provided. The description only says 'Select a track by index' without disclosing any side effects, error handling (e.g., invalid index), or behavioral details. For a simple state-modifying tool, more transparency about what happens when called (e.g., previous selection is replaced) would be helpful.

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 very concise: two sentences plus a parameter documentation line. Every part is useful and there is no redundant information.

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 simple tool with one parameter and no output schema, the description covers the essential action and parameter meaning. It also provides context that many operations require this step. Minor missing details like what happens if the index is out of bounds are not critical for a basic tool.

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 input schema has one parameter 'track' of type integer with no description. The tool's description explains it is a 0-based index, which adds crucial meaning beyond the schema. This compensates for the 0% schema description coverage.

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 clearly states the tool's purpose: 'Select a track by index.' This is a specific verb+resource pair. It also notes that many operations require selecting a track first, providing context. The name distinguishes it from sibling selection tools like 'select_tracks' or 'select_all'.

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 mentions that many operations require selecting a track first, which implies when to use this tool. However, it does not explicitly state when not to use it or provide alternatives, but the context of sibling tools makes the usage fairly clear.

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