roslyn:inline_variable

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

Describes output (variable removed, usages replaced) and coordinate system, but does not mention preview behavior or destructive nature. Without annotations, this leaves gaps.

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?

Extremely concise and well-structured with clear sections (USAGE, OUTPUT, IMPORTANT). Every sentence adds value.

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?

Covers usage, output, and critical coordinate detail. Lacks mention of preview parameter and file modification, but is fairly complete for a refactoring tool.

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 baseline 3. Description adds only coordinate system hint beyond schema descriptions, providing marginal additional value.

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 action (Inline a variable) and its effect (replacing all usages with its value), distinguishing it from sibling tools like extract_variable or rename_symbol.

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?

Explicitly instructs to position cursor on a variable declaration or usage, and notes zero-based coordinates. Lacks exclusions or alternatives, but context is clear.

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