add_work_items_to_module

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description doesn't need to restate that it's a write operation. However, it adds no additional behavioral context such as idempotency, permission requirements, or what happens if items are already in the module. The description adds no value beyond the annotations.

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 two sentences, front-loads the purpose, and provides practical instructions without any filler. Every sentence earns its place and the structure is clear and efficient.

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?

With no output schema, the description should indicate what happens on success or what is returned, but it doesn't. It also fails to explain 'project_id' or any error conditions, making the tool description incomplete for a 3-parameter 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 description coverage is 0%, so the description must compensate for all parameters. It explains the 'issues' parameter as an array of work item UUIDs and how to get 'module_id', but it omits 'project_id', which is also required. This incomplete parameter guidance is a significant gap.

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 'Add work items to a module' with a specific verb and target resource, distinguishing it from sibling tools like add_work_items_to_cycle or add_work_items_to_milestone. The purpose is 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?

The description provides explicit context by telling the agent to get work item IDs from list_work_items and module_id from list_modules, which helps with parameter sourcing. However, it does not mention when not to use this tool or name alternatives, so it lacks explicit exclusion guidance.

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