search_themes

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

The annotation readOnlyHint=true already establishes the read-only nature. The description adds no further behavioral details—such as pagination behavior, filtering semantics, or the structure of the returned list. With annotations present, the bar is lower, but the description still fails to disclose any useful behavioral context beyond what the annotation implies.

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 a single, well-structured sentence that states the purpose immediately. There is no fluff or redundant phrasing, making it highly efficient and front-loaded.

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 simple search/list tool with fully documented parameters, the description is minimally adequate. It doesn't mention the output format or how filtering works, but the schema covers parameter semantics. Given no output schema and a straightforward purpose, the description could be more informative but is not severely deficient.

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?

All three parameters (limit, offset, theme_layout_types) have descriptions in the schema, so schema coverage is 100%. The tool description itself adds no parameter-specific meaning, but since the schema already documents them, the baseline 3 applies. The description doesn't explain how theme_layout_types affects results, but the schema's enum values offer some clarity.

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 states a clear action ('Browse') and resource ('catalog of available wedding-website themes'), which distinguishes it from sibling tools like get_current_theme that target the current theme. It is specific and unambiguous, though it doesn't explicitly contrast with related tools.

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 description provides no guidance on when to use this tool versus alternatives (e.g., get_current_theme or update_current_theme). It doesn't mention typical use cases, preconditions, or exclusions. An agent would have to infer its role from the name and context.

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