palette_inspect

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful scope disclosure (only direct/local colors and CSS variables, not global palettes), but says nothing about pagination, the limit cap, or what the returned list contains. With annotations carrying the safety profile, this is adequate but not rich.

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 first and no padding; every clause clarifies scope. The only minor cost is the jargon-dense "typed inline paint styles" phrasing.

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?

An output schema exists, so return values need not be described, and the read-only nature is covered by annotations. However, with 3 parameters at 0% schema coverage, the definition leaves an agent without any guidance on required inputs or result limiting, which is a meaningful gap for an inspection tool.

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 0%, so the description must carry parameter meaning, yet it never mentions path, workspaceId, or limit. The scope of the path (which document/object) and the limit's role in truncating results are left entirely undocumented.

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 ("Lists") and resource ("direct local hex colors in attributes or typed inline paint styles, plus local CSS variable values"), and scopes it with "without reading global Inkscape palettes." This lets an agent distinguish it from palette_apply and color_management_inspect at a high level, though it never names a sibling explicitly.

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 "without reading global Inkscape palettes" gives an implicit boundary (a when-not condition), but there is no explicit statement of when to reach for this tool versus palette_apply or a broader inspection tool. Usage is implied rather than spelled out.

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