cml_batch_add_elements

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

Mentions validation before creation and the failFast parameter behavior. No annotations to contradict; however, lacks details on rollback, success/failure responses, or permission requirements. Adequate but not comprehensive.

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?

Two concise sentences front-loading purpose and key benefit. No redundant information; every word earns its place.

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?

High parameter count and no output schema; description covers general behavior but omits details on return values, error aggregation behavior beyond failFast, and atomicity guarantees. Minimum viable for a batch operation.

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 covers all 9 parameters with descriptions (100% coverage). Description adds no parameter-level detail beyond listing domain object types, so baseline 3 applies.

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?

Clear verb ('batch creation') and specific resource ('multiple domain objects' listed as entities, value objects, identifiers, events, commands, services). Distinct from individual add tools, making selection unambiguous.

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?

Indicates efficiency advantage over individual calls and pre-creation validation. Does not explicitly exclude use cases or name alternatives, but context implies single-element tools for non-batch needs.

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