Ddev Exec

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not warn that this runs an arbitrary shell command inside the container, does not state whether failures are recoverable, and does not mention the prerequisite that the project should be running.

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 single sentence is front-loaded and free of filler, which is the only positive. It is under-specified rather than genuinely concise, so it earns the minimum-viable score.

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 by structured data. But for a tool that executes arbitrary commands with no annotations, the absence of any safety, scope, or prerequisite context leaves an agent materially under-informed.

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 both parameters, so the description must compensate — and it adds no parameter information whatsoever. The meaning of 'command' (shell string? drush invocation?) and the effect of project_name defaulting to '.' are both left entirely to inference.

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 ('Execute') and resource ('command in DDEV container'), so the basic action is unambiguous. However, it makes no attempt to distinguish itself from the near-identical sibling lando_exec, so an agent must infer the difference.

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?

No when-to-use guidance at all. The sibling set contains lando_exec, ddev_start/ddev_stop, drush_command and drush_php_eval, and the description never says when this is preferable to those alternatives or whether the DDEV project must be started first.

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