tidal_palette

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

With no annotations, the description carries the full burden, and it does disclose the return shape at a high level (grouped by layer kind). It does not state that this is a static/read-only reference lookup with no side effects, nor whether results are cached or context-dependent. Adequate, but thin for a tool with zero annotation coverage.

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 front-loaded sentence with the verb and resource first and no filler. Every clause earns its place by naming the three categories (transforms, sources, controls) and the grouping dimension.

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?

With no output schema and no annotations, the description should do more to describe what an entry looks like or how the result feeds into sibling tools such as tidal_set_layer or tidal_set_control. The grouping key is mentioned, but the shape and intended downstream use of the returned entries are left implicit.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading parameter language is present.

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 verb ("Get") and a clearly named resource (a reference list of Tidal transforms, sources and controls grouped by layer kind). This is distinguishable from siblings like tidal_list_samples or tidal_get_state, which retrieve different resources. It stops short of 5 only because it doesn't contrast itself with any sibling by name.

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 phrase "that combine well" implies the use case (consulting this while building a layer), but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is inferable from the description rather than stated.

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