List Param Ids

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

No annotations are provided, so the description carries the burden. It discloses that it reads from a 'template' and the returned values are valid ids, but doesn't describe return format, potential errors, or permissions. With an output schema present, some return behavior is covered elsewhere.

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?

One succinct sentence, front-loaded with the core action and immediately followed by the relevant use case. No fluff.

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 0 params and an output schema, the description covers the essential purpose and downstream use. It lacks behavioral details like whether the list is static or dynamic, but these are not critical for correct invocation.

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?

There are 0 parameters, so no parameter semantics are needed. The baseline for 0 params is 4, and the description doesn't need to add anything.

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 (List) and resource (parameter ids from the template), and clarifies the valid domain. Distinguishes from siblings like list_presets by naming the exact resource returned.

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 parenthetical '(usable in create_preset params)' tells the agent the downstream use case, implicitly when to call it. However, it doesn't explicitly state when not to use it or name alternatives like list_presets.

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