tidal_get_samples

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

No annotations are provided, so the description carries the full behavioral burden. It indicates a read-only operation ('Get list') and names the folder, but it does not disclose how the list is returned, whether it is sorted, or whether it may fail for missing folders.

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 concise sentence that directly states what the tool returns and from where. Every word contributes meaning and there is no filler or redundant detail.

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 parameterless read-only listing tool, the description is largely complete: it names the resource and the action. It could additionally note whether the returned list is plain text, JSON, or an array, but the absence of an output schema and the simplicity of the operation keep this from being a major gap.

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?

This tool has zero parameters, so there is nothing to document beyond the schema. The description correctly introduces the sole purpose (sample names), which is sufficient for a parameterless tool.

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 a specific verb ('Get'), a specific resource ('list of available sample names'), and the source location ('Dirt-Samples folder'). This distinguishes it from sibling tools that handle evaluation, state, soloing, or history.

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 a read-only query tool with no side effects, which is distinct from sibling tools like tidal_solo or tidal_hush, but it does not explicitly state when to use it versus alternatives. The absence of parameters and the simple retrieval nature make the intended usage reasonably clear by inference.

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