trmnl_list_user_themes

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description contributes an account-level entitlement requirement, which is genuine context beyond the annotations, but says nothing about result size, pagination, or behavior when the builder is off.

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?

Three short lines, front-loaded with the purpose and the prerequisite. The trailing "TRMNL GET /api/user_themes" is endpoint trivia that adds little for an agent, but overall there is minimal waste.

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 zero-required-params, read-only list tool with full schema coverage and no output schema, the description covers purpose and the key gating condition. Only the shape of the returned theme list is left unstated.

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% with a single optional `profile` parameter fully documented, so the schema carries the burden. The description adds nothing about the parameter, which is acceptable at this coverage level.

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 my themes"), which is enough to distinguish it from create/get/update/delete/import user theme siblings by name. It does not explicitly say how it differs from trmnl_get_user_theme, but the list-vs-single distinction is implied by the verb.

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?

Adds a real precondition ("Requires the theme builder to be enabled for the account") that tells the agent when the call is valid. However it never names the alternative for fetching a single theme or says what to do when the builder is disabled.

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