Strict Archive-Filtered Palette from Concept

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

Annotations include readOnlyHint=true, and description does not contradict that. Description adds the behavioral context of solving cross-archive drift, but does not disclose other traits like auth needs or rate limits. Annotations already cover safety, so this is adequate but not outstanding.

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?

Three sentences, front-loaded with the key comparison. Every sentence provides useful information: differentiation, usage, and rationale. No wasted words.

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?

Given the presence of output schema (not shown but known from context), description need not explain return values. It covers purpose, parameters, and usage context sufficiently for a 5-parameter tool with 1 required. No gaps.

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 coverage is 100%, but description adds value by explaining the purpose of allowed_archives ('restrict to specific cultural traditions') and min_relevance ('filter weak concept matches'), with examples. This goes beyond the schema's brief descriptions.

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?

Description starts with 'Like palette_concept but with archive filtering and relevance controls', clearly distinguishing it from sibling. It specifies verb 'generate' or 'create' implied, and resource 'palette' with strict filtering. No ambiguity.

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?

Explicitly states when to use: 'when cultural specificity matters' and 'Fixes cross-archive drift'. Gives examples for allowed_archives and min_relevance. Does not explicitly state when not to use, but context makes it clear.

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