agy_refactor

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

With no annotations, the description must fully disclose behavior, but it only mentions return style ('without conversational fluff'). It does not state whether the file is modified in place, permissions required, reversibility, or failure behavior, which is critical for a refactor tool.

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?

Two short sentences front-load the action and result, with no filler. It is appropriately concise for the minimal info it conveys.

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 mutation-capable tool with three parameters, no output schema, and no annotations, the description is underspecified. It omits how changes are applied, what 'code changes' means (diff vs. full file), and how the optional model affects behavior. This falls well short of a complete tool description.

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 already describes filePath and instructions, and the description aligns with those. The optional 'model' parameter is undocumented in both schema and description, and description adds no extra meaning beyond the schema's coverage of required parameters.

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 uses specific verb 'Refactor' and resource 'target file', clearly indicating the operation. It adds return behavior ('Returns code changes') and a tone guideline, but does not explicitly distinguish from sibling tools beyond the action verb.

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 agy_analyze or agy_chat. It lacks context, prerequisites, or exclusions, leaving the agent to infer applicability from the name alone.

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