trmnl_get_user_theme

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds genuinely new context: the scss field is the framework stylesheet, identical to what the builder downloads, and access requires the theme builder feature. It omits anything about what else is returned or behavior when the feature is disabled.

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, front-loaded statements with no filler; the scss clarification and prerequisite each earn their place. Minor formatting awkwardness from the line break mid-sentence.

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 read-only tool with no output schema, the description should say what the returned theme object contains beyond scss (name, timestamps, etc.). The `profile` parameter and the error condition when the theme builder is disabled are left unaddressed.

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?

At 50% schema coverage, the description compensates somewhat by tying the call to /api/user_themes/{id}, reinforcing that path.id is the theme id. However, the nested `path` wrapper and the `profile` parameter receive no explanation beyond the schema's one-liners.

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 ("Read a theme") and clarifies the payload includes the exported SCSS framework stylesheet. It is clearly not a list/create/update tool like its user_theme siblings, though it doesn't explicitly name them.

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?

Provides one real prerequisite (theme builder must be enabled for the account) and an implied single-theme-by-id use case. It never contrasts with trmnl_list_user_themes or explains when to fetch one theme instead of listing all.

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