Drush Command

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

With no annotations, the description carries the full behavioral burden, and it delivers unusually rich detail on options handling: flags take no value, True renders as --yes, False omits the flag, and the historical bug where False silently passed --yes and suppressed confirmation on destructive commands. This surfaces real operational danger. It stops short of noting privilege/permission implications of arbitrary command execution.

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 core purpose is front-loaded in one line, which is good, but it is followed by two long, narrative paragraphs that recount a fixed bug rather than state current behavior. The material is repetitive ('that direction was the dangerous one, because it used to pass --yes') and larger than the actionable content warrants.

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?

An output schema exists, so return values are covered. But for a broad arbitrary-execution catch-all, the definition omits command/args semantics and any guidance on preferring the numerous specialized siblings, leaving real gaps an agent would face when choosing and invoking 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%, so the description must compensate, and it does so thoroughly for options (rendering rules, booleans, omission semantics). But command and args receive no explanation at all, leaving two of three parameters undocumented in both schema and description.

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 opening sentence states a specific verb and resource: execute any Drush command. So the purpose is immediately clear. However, it offers no differentiation from the many dedicated drush_* siblings (drush_cron, drush_updb, drush_watchdog, cache_rebuild, cache_clear), so an agent cannot tell from the description when this catch-all is preferred over those.

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?

There is no when-to-use guidance, no exclusions, and no routing to specialized alternatives that already exist as siblings. The description focuses entirely on how options are serialized, saying nothing about when this generic escape hatch should be chosen over the purpose-built drush tools.

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