trmnl_list_models

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds almost nothing beyond that — only the implicit "all" (no filtering/pagination) and a raw API path, with no mention of auth, rate limits, or result shape.

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, action front-loaded, nothing superfluous. It is appropriately sized for a trivial read-only list operation.

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-parameter list tool with full annotation coverage and a fully documented schema, the description is sufficient to call it correctly. It could note what a "model" contains or whether results are paginated, but that is a minor gap with no output schema to fill in.

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 description coverage is 100% and the single `profile` parameter is documented in the schema with its default behavior, so the baseline of 3 applies. The description never mentions `profile` or how it selects which TRMNL configuration to query.

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 device models"), which is clearly distinct from nearby siblings such as trmnl_list_devices or trmnl_list_palettes. It does not explicitly contrast itself with those siblings, but the resource name is 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?

There is no guidance on when to call this versus trmnl_list_devices, trmnl_get_device, or trmnl_identify_device. The second line ("TRMNL GET /api/models") is an endpoint reference, not usage context or prerequisites.

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