copy_cases_to_section

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 states 'copy' but does not clarify if this creates duplicates, retains originals, requires permissions, or handles errors. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its effects and requirements.

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 with zero waste—'Copy test cases to another section'—front-loading the core action. It is appropriately sized for the tool's complexity, with no redundant or verbose elements.

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 involves mutation (copying cases) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., duplication effects, permissions), error handling, or return values. For a tool with two required parameters and potential side effects, more context is needed to ensure safe and correct usage.

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?

The schema description coverage is 100%, with clear descriptions for 'section_id' (target section ID) and 'case_ids' (array of case IDs to copy). The description adds no additional semantic context beyond what the schema provides, such as format details or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 verb 'copy' and the resource 'test cases', specifying the destination 'to another section'. It distinguishes from the sibling 'move_cases_to_section' by implying copying rather than moving, though this distinction could be more explicit. The purpose is specific and actionable.

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 like 'move_cases_to_section' or 'add_case'. It lacks context about prerequisites, such as whether the source cases or target section must exist, or any constraints on copying. Usage is implied only by the action described.

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