refactor

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

With no annotations provided, the description carries the full behavioral burden and does well: it explains that the command applies changes, that `dry_run` checks readiness without applying changes, that timeouts default to 600 seconds and can be disabled, and that failures raise `ToolError` with partial output. It does not explicitly mention file-system side effects, but 'apply automated refactorings' implies mutation clearly enough.

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 well-structured with clear sections for overview, arguments, return value, and errors. It is somewhat redundant with the schema's parameter descriptions, but the added details earn their place and the opening sentence front-loads the core purpose.

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?

The description is complete for this CLI-wrapper tool: it covers the command being run, all parameter defaults and behaviors, the return structure, and failure modes. An agent has everything needed to invoke the tool correctly without relying on external documentation.

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 the baseline is 3. The description adds meaningful value beyond the schema by explaining that `path` searches the system PATH and the DIFFBLUE_COVER_CLI environment variable, that `dcover_timeout=None` disables the timeout, and that `dry_run` avoids applying changes. These details help an agent call the tool correctly.

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 a specific verb and resource: 'Invoke Diffblue Cover to refactor the project' and identifies the exact command executed (`dcover refactor`). It also gives concrete example use cases ('fixing build issues or adding missing dependencies'), which makes the tool's purpose unmistakable and distinct from the sibling tools.

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 clear context for when to use the tool: applying automated refactorings, fixing build issues, or adding missing dependencies. It does not explicitly contrast with the sibling tools `create` and `issues`, but it gives enough purpose-based guidance for an agent to select it appropriately.

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