list_takes

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

readOnlyHint=true already establishes that this is a safe read; the description adds that the result also indicates 'which is active', which is genuine behavioral context about the response. It stops there, saying nothing about ordering, take metadata, or whether inactive takes are always included, so it is useful but thin.

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 short sentence with no filler, and the resource being operated on is front-loaded. It is efficient, though it sacrifices clarity for brevity by dropping the verb.

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 one-parameter read-only tool with full schema coverage this is close to sufficient, but with no output schema the description is the only place to convey the shape of the response, and 'which is active' does not tell the agent what else a take record contains or how to reference one for choose_take.

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 single item_id parameter is 100% documented in the schema, including the provenance (create_midi_item/get_track_details) and the 'selected' sentinel, so the schema already carries the semantics. The description's phrase 'in an item' adds no format or syntax detail beyond that, making the baseline 3 correct.

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 fragment 'The takes in an item ... and which is active' conveys the resource (takes within an item) and a hint at return content, but omits an explicit verb like 'List' and reads as a caption rather than a directive. It also does not distinguish itself from siblings such as choose_take or explode_takes, which also operate on takes.

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?

There is no when-to-use guidance and no mention of alternatives, despite three take-related siblings (choose_take, explode_takes) whose relationship to listing is exactly what an agent needs spelled out. The agent must infer that this is the discovery step before choosing or exploding.

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