rolldev_composer

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions running commands 'inside the php-fpm container' but doesn't cover critical aspects like permissions needed, whether it's read-only or destructive, error handling, or output format. For a tool that executes commands in a container, this lack of behavioral context is a significant gap.

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, clear sentence with zero waste. It's front-loaded with the core purpose and efficiently conveys the essential information without unnecessary elaboration.

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 running commands in a container, the lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, output expectations, or error conditions, which are crucial for an agent to use this tool safely and effectively.

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 fully documents all parameters. The description adds no additional semantic context about the parameters beyond what's in the schema, such as explaining the relationship between 'project_path' and the container or elaborating on 'command' examples. 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 Composer commands') and the execution context ('inside the php-fpm container'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'rolldev_php_script' or 'rolldev_magento_cli', which might also involve container execution or PHP-related commands.

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. With siblings like 'rolldev_php_script' and 'rolldev_magento_cli' that might overlap in context, there's no indication of when this Composer-specific tool is preferred or what scenarios it's designed for.

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