command_refactor

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. 'Safely refactor' is vague; it does not clarify what 'safe' means, whether tests are run, if code is modified, or if the operation is destructive. Minimal transparency beyond the headline.

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, focused sentence with no wasted words. It is efficient and front-loaded with the key 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?

For a refactoring tool, the description lacks detail on required prerequisites, side effects, return values, or error conditions. Given no output schema and sparse annotations, more context (e.g., 'requires passing tests', 'modifies files in place') would be needed for complete understanding.

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 input schema already describes the single 'arguments' parameter with examples (file path, flags). The tool description adds no additional meaning or constraints beyond what the schema provides. Schema coverage is 100%, so 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 the verb ('refactor'), the resource ('code'), and the method ('with test verification'). It distinguishes itself from sibling tools like command_fix_bugs or command_test by indicating a safe, test-verified refactoring approach.

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 implies usage for safe refactoring with tests, but it does not explicitly state when to use this tool versus alternatives like command_detailed_review or command_fix_bugs. No exclusions or context are provided.

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