list_presets

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

With no annotations, the description must convey behavior. The verb 'list' clearly indicates a read-only operation with no side effects, but it does not explicitly state that no modifications occur. Given the inherent safety of listing, this is adequately transparent.

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 a single, compact sentence with no redundant words. It conveys all necessary information efficiently, earning full marks for conciseness and structure.

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 list operation, the description fully covers what the tool does, including the target (player) and the types of presets. Output details are handled by the output schema, so no additional context is needed.

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 parameter 'player' has no schema description, but the tool description references 'on a player,' providing sufficient context to infer its role. This adds meaning beyond the raw schema, though a direct description of the parameter's expected format would improve clarity.

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 action (list), the resource (presets), and the scope (on a player). It also enumerates the types of presets (radio stations, playlists, inputs), making the purpose unambiguous and distinguishable from sibling tools like load_preset.

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 implies usage (list presets for a player) but does not explicitly contrast with alternatives or state when not to use it. While the context is clear, it lacks direct guidance on choosing this over other tools like browse or load_preset.

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