trmnl_list_palettes

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds only the endpoint path (GET /api/palettes), not any context on authentication, response shape, or pagination.

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?

Two short lines, front-loaded with the action, with no filler. The endpoint-path second line is of marginal value but not harmful.

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 read-only list with no output schema, the description is barely sufficient: it doesn't indicate what a palette contains or what the response looks like. Annotations cover safety, so the main gap is domain meaning rather than behavior.

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?

Only one optional parameter (`profile`) exists and the schema documents it at 100% coverage, so the schema carries the semantics. The description adds nothing about how profile selection changes the result set, which is the minimum acceptable baseline.

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 and resource ("List all palettes") and adds the underlying API route, so the operation is identifiable. It does not clarify what a palette actually is in TRMNL's domain (color scheme vs. theme), though no sibling tool competes for the same name.

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?

There is no guidance on when to call this versus related listing tools such as trmnl_list_user_themes or trmnl_list_categories, and no prerequisites or exclusions are mentioned. Usage is only inferable from the verb "List".

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