copyToSection

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

Given no annotations, the description should disclose behavioral details like permissions, error handling, or side effects. It only states the basic copy action, missing any transparency beyond that.

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?

A single, concise sentence in English and Japanese. It is front-loaded and efficient, with no redundant information. However, it could be slightly more structured by including a note about similar tools.

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?

For a simple tool with two parameters, the description covers the basic function. However, it lacks details about what the tool returns, potential errors, or ordering, making it just adequate.

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 coverage is 100%, so the schema already describes parameters. The description adds no extra meaning beyond 'specified test cases' and 'target section'. Baseline 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 it copies test cases to a target section while preserving originals, using 'copies' as a specific verb. It implies the difference from the sibling tool moveToSection, but does not explicitly call it out. Purpose is clear and distinct.

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?

No guidance on when to use this tool versus alternatives like moveToSection, or any prerequisites. The description only states what it does, not when it should be used or avoided.

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