photographi_get_color_palette

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

No annotations exist, so description bears full burden. It discloses the algorithm (K-Means), read-only nature (extraction), and output format. Lacks details on error handling or resource usage, but is adequate for a simple extraction tool.

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, each serving a distinct purpose: purpose+method, output+default, usage guidance. Front-loaded, 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 output schema exists, return value explanation is adequate. Tool is simple with 2 params; description covers key behavior. Minor omission: no mention of valid image formats or error cases, but overall sufficient.

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 covers image_path with description but not colors. Description adds default value and output format context for colors, and implies image_path is absolute, adding value beyond schema's 50% coverage.

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 clearly states it extracts a color palette from a single image using K-Means clustering, and lists output as hex codes. It distinguishes from sibling tools like photographi_get_folder_palettes (folder-level) and photographi_analyze_photo (broader analysis).

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?

Provides a use case ('design inspiration or color grading reference') but does not explicitly exclude alternatives or specify when not to use this tool over siblings like photographi_get_folder_palettes for batch palette extraction.

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