List themes

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

With no annotations available, the description carries the full burden of behavioral disclosure. It clearly states a read-only enumeration behavior ('List all themes') and exposes that it returns roles including live, unpublished, and development. The verb 'list' strongly implies no mutation, though an explicit 'read-only' statement would have been slightly more transparent.

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 sentences: the first front-loads the action and output details, the second adds a practical usage hint. There is no filler, and every sentence earns its place.

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?

The description gives the essential return value (IDs, roles) and a usage directive, which is sufficient for a zero-parameter list tool. Since no output schema exists, the description fills the gap with the key fields, though it could have been slightly more explicit about the shape of the returned list.

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?

The tool has zero parameters and an empty schema, so the 100% schema coverage makes parameter documentation moot. The description correctly avoids inventing parameters and focuses on the output, which is appropriate for a zero-parameter tool.

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?

The description uses the specific verb 'List' and names the resource ('all themes in the store'), and adds key output details (IDs and roles with allowed values live, unpublished, development). This clearly distinguishes it from sibling operations like publish_theme or theme_pull, which act on themes rather than enumerate 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?

The sentence 'Use this first to find theme IDs' explicitly identifies the intended context for this tool. However, it does not name any sibling alternatives or state when not to use it, so it stops short of the full when/when-not/alternatives guidance.

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