palette_convert

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It describes the conversion operation but does not mention side effects, idempotency, error conditions, or output format details. For a simple conversion tool, this is adequate but minimal.

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 sentence that packs all essential information: action, input source, output targets. No wasted words, well-structured and front-loaded.

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 no output schema and no annotations, the description covers the core purpose and inputs adequately. It specifies the input source and output formats, which is sufficient for a straightforward conversion tool. It could add details about the output (e.g., string or file) but not strictly necessary.

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%, so the input schema already documents both parameters adequately. The description adds little new meaning beyond restating that 'palettes' come from palette_fetch (already in schema) and enumerating target formats (already in enum). It does not explain the format or constraints of palettes beyond the schema.

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 the action (convert) and the resource (palette JSON from palette_fetch) and specifies the supported target formats (CSS, Tailwind, SCSS, Figma tokens, Android XML, Swift). It is specific and distinguishes this tool from sibling tools like palette_fetch.

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 when to use this tool: after obtaining palette JSON via palette_fetch. It mentions the source and target formats, providing clear context. However, it does not explicitly state when not to use it or list alternatives, though the sibling set includes other conversion tools like generate_css_output.

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