event_list_tracks

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

Annotations are absent, so the description carries the burden. It notes the output includes mixer-group name and both GUIDs, but doesn't disclose error behavior, edge cases, or side effects. For a read-only listing, it's adequate but 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?

Two-sentence description plus a brief parameter list. Every word adds value; no fluff.

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?

Core information is present, but the return structure is only vaguely implied ('both guids each') and error behavior is not discussed. For a simple listing operation, it's mostly sufficient, but more detail on the exact return shape would help.

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 has no descriptions and coverage is 0%, so the description compensates by documenting 'target' as event:// path or GUID and 'include_master' with its default. This adds meaningful semantics beyond the raw 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?

Clear verb+resource: 'List an event's group tracks' with explicit mention of output contents ('mixer-group name + both guids each'). Differentiates from sibling tools like event_list and mixer_group_info by focusing on tracks within an event.

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 exclusions or alternatives provided. The description implies it's for retrieving track-level details of an event, but doesn't contrast with related tools or state when to use this instead of another.

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