find_dj_candidates

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

The description lacks detail on behavior such as how results are ranked, whether it searches personal or global catalog, or how parameters interact. With no annotations, the description should provide more transparency but is minimal.

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 a single sentence, which is concise, but it is under-specified for a tool with 7 parameters. It lacks structure and fails to earn its place by conveying necessary 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?

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is critically incomplete. It does not explain return values, prerequisites, or parameter usage, leaving the agent underinformed.

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%, meaning the description must explain parameters. It mentions BPM/key/genre but does not clarify which schema properties correspond, nor does it explain camelot_key, limit, include_missing_metadata, or bpm_min/max semantics.

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 finds DJ playlist candidates by BPM/key/genre, which is a specific action and resource. It distinguishes from sibling tools like auth_status or list_liked_songs.

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for music discovery based on musical parameters, but does not address alternatives or context.

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