cml_add_command

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It merely states the action without mentioning any side effects, validation, or constraints (e.g., what happens if the command already exists or if the aggregate requires specific conditions).

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 sentence, which is concise but lacks informational depth. It earns its place without waste, but it is too brief to provide substantial value. An average score is appropriate.

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 tool complexity (a mutation in a DDD modeling context) and the absence of an output schema, the description should explain what happens after the command is added (e.g., return value, effect on the model). It does not, leaving the agent with incomplete information.

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 each parameter has a description in the schema itself. The tool description adds no additional meaning beyond the schema. According to the rubric, with high schema coverage, the baseline score is 3 even with no extra parameter info in the 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 description 'Add a command to an aggregate' clearly states the action (add), the resource (command), and the target (aggregate). It effectively distinguishes this tool from sibling tools like cml_add_domain_event or cml_add_entity, which add other types of elements.

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, nor does it mention prerequisites or context. While the name suggests its purpose, the description lacks explicit usage context, which is insufficient given the many sibling tools.

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