detect_track_key

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

Discloses read-only behavior with 'Reads only; changes nothing,' which reinforces the readOnlyHint annotation. Also mentions the algorithm (Krumhansl-Kessler) and the effect of the weight parameter. No contradictions.

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?

Four well-structured sentences. First sentence states purpose and method, second provides use case, third explains parameter, fourth states safety. No superfluous words, front-loaded efficiently.

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 tool's simplicity (2 parameters, output schema present), the description covers all necessary aspects: purpose, usage, parameter meaning, and behavioral safety. No gaps.

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?

Schema coverage is 0% (no descriptions in schema), but the description explains the 'weight' parameter with valid options ('duration', 'velocity', 'product', 'count'). The 'track_index' parameter is not described, but it is self-evident from context.

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?

Clearly states the action ('Detect the key/scale'), the resource ('whole track'), and the method ('pooling the notes of every Session clip it holds'). Distinguishes from sibling tools like 'detect_clip_key' and 'detect_session_key' by specifying the scope.

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?

Provides explicit use case: 'Useful when a part is spread across several clips.' This implies when to use this tool over single-clip alternatives, though it does not explicitly name the alternatives or state when not to use.

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