lexicon_search_tracks

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

No annotations are provided, so the description carries the full burden. It only states the action (search) but does not disclose whether it is read-only, any authentication needs, rate limits, or side effects. The description lacks behavioral transparency.

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 concise, with a brief introductory sentence followed by well-formatted examples. It is front-loaded and efficient, though examples could be better organized with a brief explanation of filter syntax.

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 complexity (nested object parameter, no output schema), the description lacks information about the return format, pagination, or any limits. The examples are helpful but do not fully cover the filter object's capabilities.

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 schema only describes 'filter' as an object with no constraints. The description adds significant value by showing example filter contents (tags, artist, location) and syntax, which is essential for correct usage.

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: 'Search tracks using Lexicon filters.' It uses specific verb 'Search' and resource 'tracks', and distinguishes from sibling 'lexicon_list_tracks' by emphasizing filters.

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 explicit examples of filter usage, making it clear when to use this tool (for filtered searches). It does not explicitly state when not to use or name alternatives, but the context is clear.

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