get_palette

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but it does not explain return format (e.g., array of RGBA values), behavior when no sprite is open, or whether the palette is document-global. Lacking output schema, these details remain undisclosed.

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, front-loaded sentence with no redundant words. It efficiently conveys the tool's purpose without padding.

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 tool's simplicity (no params, no output schema), the description provides the core purpose but leaves out return value structure and error conditions. For a minimal getter, this is adequate but not fully complete, as agents would benefit from knowing the palette color format.

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 input schema has zero parameters, so no parameter descriptions are needed. The description correctly omits param details, and the baseline for a 0-param tool is applied.

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 a specific verb ('Get') and resource ('current palette colors of the active sprite'), making the tool's action unambiguous. It also differentiates from sibling tools like set_palette_colors, load_palette_from_file, and resize_palette by emphasizing retrieval of the current state.

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 the tool is for reading the active sprite's palette, but it does not explicitly state when to use it over alternatives such as set_palette_colors or load_palette_from_file. Context is clear for a simple getter, but no exclusions or alternative references are provided.

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