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

With no annotations provided, the description fully discloses behavior: it states 'Read-only; no side effects' and 'Returns null if no palette by that name exists.' This gives the agent a clear safety and error-handling context, going beyond minimal requirements.

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 three sentences, each serving a distinct purpose: primary action, return behavior, and usage guidance. It is front-loaded with the core purpose and contains no filler or redundant restatements.

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 one-parameter read-only tool, the description covers purpose, behavior (null return, read-only), usage context, and alternatives. Given the available output schema, the information is complete and sufficient for an agent to invoke the tool correctly.

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?

The only parameter 'name' is clarified through the description's repeated references to 'by name' and the null condition for missing names. With 0% schema description coverage, this fills the gap and tells the agent exactly what the parameter represents, though it could have been more explicit.

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 explicitly states 'Retrieve one saved palette by name' with a specific verb and resource, and distinguishes itself from siblings by noting that 'list_palettes' provides all names and 'save_palette' handles creation/updates. This makes the tool's function unambiguous.

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?

It gives clear guidance: 'Use when you already know the palette name' and directs users to 'list_palettes' for listing names and 'save_palette' for modifications. This explicitly covers when to use this tool and when to choose an alternative.

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