lexicon_list_incoming

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

No annotations provided. The word 'list' implies a read-only operation, but the description does not explicitly state that it is non-destructive, nor does it mention any side effects, permissions, or behavior when the queue/watch folder is empty.

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 sentence of 15 words that is direct and contains no redundant information. It efficiently communicates the tool's basic purpose.

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 lack of output schema and annotations, the description is too minimal. It does not explain the difference between 'Incoming queue' and 'watch folder', default behavior, ordering, or error handling, leaving the agent underinformed for a potentially nuanced 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 schema contains one optional parameter 'limit' (integer, min 1, max 200) with 0% description coverage. The description does not mention this parameter or its effect on results, providing no added value over the schema.

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?

Description clearly states 'List tracks' and specifies the scope: 'Incoming queue or under DJ-incoming watch folder'. This distinguishes it from sibling tools like lexicon_list_tracks which lists all tracks, but the 'or' introduces slight ambiguity about when each source is used.

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 guidance on when to use this tool versus alternatives like lexicon_list_tracks or lexicon_list_playlists. The context of 'Incoming queue' suggests a specific workflow, but the description does not clarify the purpose or prerequisites.

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