ddev_composer_command

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides minimal information. It mentions running a command but doesn't disclose execution context (e.g., where it runs, permissions needed), potential side effects (e.g., package installation/modification), error handling, or output characteristics. For a command execution tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple command execution tool and front-loads the essential information. Every word earns its place with zero waste.

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 the complexity of command execution tools and the absence of both annotations and output schema, the description is insufficiently complete. It doesn't explain what happens when the command runs (e.g., execution environment, output format, error conditions), nor does it address common use cases or limitations. For a tool that could have significant behavioral implications, more context is needed.

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 100%, so the schema already documents both parameters ('command' and 'project_name') with their types and descriptions. The description adds no additional parameter semantics beyond what the schema provides—it doesn't clarify command syntax examples, project_name defaults, or parameter interactions. The baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Run') and target ('a Composer command in the DDEV project'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'ddev_exec_command' which might also run commands, leaving some ambiguity about when to use this specific Composer-focused tool versus general command execution.

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. There's no mention of when to choose this Composer-specific tool over 'ddev_exec_command' for general commands, or whether it should be used instead of direct Composer execution outside DDEV. No prerequisites, exclusions, or contextual boundaries are specified.

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