List demos

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

The description discloses sorting order, the exact fields returned, and the case-insensitive substring filtering behavior for the stage argument. While no annotations are provided, this covers the most important behavioral traits for a read/list operation.

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 concise, front-loaded sentences cover purpose, output fields, usage triggers, and a filter parameter without wasted words. Each sentence earns its place, making it easy to parse quickly.

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?

Since there is no output schema, the description correctly enumerates the item fields (artist, title, status, date, score), explains sorting, and gives usage scenarios. The schema already handles parameter details, so nothing essential is missing.

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 description coverage is 100%, so the baseline is 3. The description adds minor redundancy with examples ('listening', 'interested', 'pass') but does not meaningfully enhance understanding beyond the schema's existing parameter descriptions.

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 opening sentence specifies the exact function: 'Lists demo submissions from the Berbotu vault, sorted newest-first by received_date.' This includes a specific verb, resource, and sorting detail, clearly distinguishing it from siblings like list_releases and add_demo.

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?

It explicitly states when to use: 'Use this when the user asks about incoming submissions, the demo pipeline, A&R inbox, or anything like...' This provides strong contextual guidance, though it does not name alternatives or state when not to use it, so it falls short of a 5.

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