get_selected_items

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

The description adds minimal behavioral info: it states the return type ('Object with list of selected items') but does not clarify the structure of that object (e.g., item IDs, names, or how to access the list). The readOnlyHint annotation already covers safety, so the description's contribution is limited but not contradictory.

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 extremely concise with two short sentences, no fluff, and the primary action is front-loaded. It earns its place entirely.

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?

Without an output schema, the description should explain the return value in more detail. 'Object with list of selected items' is vague about what constitutes an item and how to parse the object. However, for a simple read-only getter with no parameters, it may be adequate for an agent familiar with the domain.

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?

There are zero parameters, so the description correctly has no parameter details. Per the baseline for 0-param tools, this is a 4; no additional explanation is needed.

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 verb 'get' and the resource 'selected media items', which distinguishes it from siblings like get_selected_tracks and get_selected_midi_notes. The purpose is unambiguous.

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 guidance is provided on when to use this tool versus alternatives (e.g., get_selected_tracks, select_all_items). The description does not mention when not to use it or any context for selection scope, leaving the agent to infer.

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