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

Since there are no annotations, the description must carry the behavioral burden. It significantly adds value by detailing exactly what fields the agent can expect to receive in the response (name, slug, primary color, scene, and tag), providing vital structural context.

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 highly concise, using a single sentence to convey the tool's function, available filters, and the specific set of data fields returned. There is zero wasted information.

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 filtering/listing tool, the description is completely adequate. It defines the available parameters and clearly states the structure of the expected output data fields, leaving no critical operational gaps for the agent.

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?

Schema description coverage is 100%, setting a baseline of 3. The description reinforces the filtering functionality (platform and tag) and the default scope ('if not filled, all three are listed'), but it does not add critical semantic meaning beyond what the existing schema parameters already define.

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 uses a clear verb ('list') and specifies the resource ('color palettes in the library'). Crucially, it defines the operation as a listing and filtering task, distinguishing it from tools like get_palette or suggest_palette.

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 clearly outlines the mechanisms available for selecting data (filtering by platform and tag). This defines the scope of usage, implying its use for broad data retrieval rather than focused retrieval, though it does not explicitly state 'when not to use get_palette'.

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