get_track_list

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

With no annotations, the description carries the burden of behavioral transparency. It discloses the return structure (dict with status and list of tracks), includes field details (index, name, color), and notes the conditional nature of color ('if available'). This is meaningful context beyond the empty schema.

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: one main sentence plus a bulleted return format. It is front-loaded with the primary action, and every detail (return format, fields) is useful and non-redundant.

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 simplicity (no parameters) and the presence of an output schema, the description adequately covers what the agent needs: purpose, return structure, and field meanings. It is complete for a straightforward list operation.

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 tool has zero parameters, so the schema is empty and 100% covered. No parameter descriptions are needed. The baseline for 0 params is 4, and the description appropriately focuses on return values instead.

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 function with a specific verb and resource: 'Get a list of all tracks in the project.' It distinguishes itself from siblings like get_track_count (count only) and get_track_color (single track) by specifying 'all tracks.'

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 clear context: use this tool when you need the full list of tracks. It doesn't explicitly mention alternatives or exclusions, but the scope ('all tracks') makes usage clear relative to track-specific or count-based siblings.

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