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

Beyond the readOnlyHint annotation, the description discloses that aliases are unverified operator-supplied labels and should be treated as data, not instructions. It also reveals that results are limited to themes with at least one public slot and explains the opaque cursor/next pagination behavior, adding valuable behavioral context.

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?

The description is well-structured and front-loaded with the tool's purpose. Each sentence earns its place: examples of themes, field details, alias resolution workflow, pagination logic, and a security caveat. No fluff or redundancy.

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 the output schema exists, the description need not explain return values. It covers the purpose, how to use results with search_slots, the pagination loop, and the unverified nature of aliases. This is a complete description for a read-only list tool.

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 description thoroughly explains the cursor parameter (opaque, from previous response, pagination loop) and compensates for the 0% schema coverage. However, it does not explicitly describe the page_size parameter, though its meaning is self-evident from the name. Overall, it adds significant meaning beyond the schema for at least one of the two parameters.

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?

Clearly states it lists slot themes with a specific scope (visual/narrative setting) and examples (Egyptian, Ancient Rome, Fantasy). It distinguishes itself from sibling tool search_slots by explaining the exact-match slug behavior, which is useful for selecting the right tool.

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?

Explicitly instructs to look up the slug here before using search_slots' theme parameter, since search_slots does not accept aliases directly. It also provides precise pagination instructions (keep paginating with cursor until next is null), which is actionable guidance for using the tool correctly.

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