search_keyCompatible

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

No annotations are present, so the description must disclose behavior. It mentions the Camelot mixing rules, adding algorithmic context. However, it does not describe the response format, ordering, or any side effects (though read-only is likely).

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 concise sentence that immediately states purpose and method. No redundant or filler content.

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?

The description lacks details about return structure, pagination behavior, and compatibility criteria beyond 'Camelot rules'. With no output schema or annotations, these gaps are more significant.

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?

Only the 'key' parameter has schema description; the tool description adds context about the source key and Camelot code. The 'limit' and 'offset' parameters are not described in the description, relying solely on their self-explanatory names and defaults.

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 function: finding tracks compatible with a source key using Camelot harmonic mixing rules. The verb 'Find' and specific resource 'tracks' make it distinct from generic sibling search tools like library_search.

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 implies the use case—when harmonic compatibility is needed—but does not explicitly compare against alternatives or state exclusions. No guidance is provided for when to prefer this over library_search or setlist_suggestTransitions.

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