Theme Info

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the two underlying mechanisms (drush pm:list and a YAML parse of the theme's .info.yml), that it walks the base-theme chain upward, and that it requires a local docroot/DRUPAL_ROOT. It stops short of stating failure behavior for a missing theme or the read-only guarantee explicitly.

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?

Front-loaded single-line purpose followed by a compact explanation of data sources and the DRUPAL_ROOT requirement; no filler sentences. The second paragraph is dense but each clause carries information.

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 an output schema exists, return values need not be described, and the description covers the input expectation, data provenance, and environment prerequisite. It could note behavior when the theme is absent or whether sub-themes are traversed, but nothing critical is missing for calling it.

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 coverage is 0% and the sole parameter theme_name has no schema description. The description only implies it via 'one theme' and 'the theme's own .info.yml'; it never clarifies whether the value is a machine name or a label. Marginal added meaning over the bare schema.

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 ('Describe one theme') and then enumerates exactly what is returned (metadata, base-theme chain, regions, libraries), so the agent knows this is a deep-inspection tool rather than a search or list. It does not name or contrast any sibling (e.g. theme_get, theme_active, theme_search), so it falls just short of the top band.

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 supplies an environment precondition ('Requires DRUPAL_ROOT: the info.yml lives on the local docroot'), which tells the agent when the tool can actually run. However, it never states when to prefer this over theme_search, theme_get, or theme_active, so usage selection is left implied.

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