get_track_items

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

Annotations already mark the call read-only, so no mutation disclosure is needed, but the description adds only a generic return shape and no information about indexing, empty results, ordering, or error behavior. It provides little behavioral context beyond what the name and annotation imply.

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 short sentences with no filler, front-loaded with the action. It is concise but sacrifices needed detail, so it earns high marks for structure rather than perfect marks.

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?

For a simple getter this is close, but with no output schema and no parameter explanation, the description fails to fully equip an agent to call it correctly. The return statement is too vague to know what the item list contains.

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 input schema exposes only a bare integer track_index with 0% description coverage, and the description never defines the index base, scope, or what 'track' refers to. An agent is left to guess whether the index is 0-based, 1-based, or a track ID.

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?

States a specific action and resource: retrieve all media items for a track. The phrase 'all media items' distinguishes it from singular tools like get_midi_item or get_item_info, and the return statement reinforces what the tool produces.

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 offers no guidance on when to choose this tool instead of siblings such as get_takes, get_item_info, or get_track, nor does it explain how track_index should be interpreted. Usage is only implied by the tool name and verb phrase.

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