Theme Search

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about this being a remote network call, rate limits, result ranking, or pagination behavior. An output schema exists, but behavioral traits beyond return shape are undisclosed.

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?

A single efficient sentence with no filler, front-loading the verb and resource. It is arguably too terse given the gaps, but nothing is wasted.

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 remote search tool with 3 undocumented params and no annotations, the description leaves pagination, result scope, and source-API behavior unaddressed. The output schema covers return shape, but call correctness still depends on details not provided.

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 0% for 3 parameters, so the description must compensate and largely doesn't. 'By name or description' loosely maps to the query parameter, but page and page_size are undocumented anywhere, leaving pagination semantics unspecified.

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 ('Search Drupal.org for themes') plus the searchable fields ('name or description'), which distinguishes it from siblings like theme_get (retrieve a single theme). Lacks an explicit sibling contrast, but the purpose 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?

Implies discovery of remote Drupal.org themes but gives no when-to-use vs. when-not guidance and names no alternatives (e.g. theme_get for an existing theme, module_search for modules). The agent must infer the context.

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