roslyn:extract_method

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

No annotations provided, so description carries full burden. Mentions data flow analysis and zero-based coordinates, but does not disclose that the tool modifies files, requires a loaded solution, or any potential side effects. The output fields are mentioned but not detailed.

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?

Five sentences covering purpose, usage, output, workflow, and a crucial note. Well-structured and front-loaded. Could be slightly condensed but overall efficient.

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?

No output schema provided, but description covers key output fields (extractedCode, replacementCode). Missing prerequisites (e.g., solution loaded) and error conditions. Sufficient for basic usage but not exhaustive.

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%, baseline 3. Description adds value by clarifying that startLine/endLine must contain complete statements, preview flag defaults to true, and coordinates are zero-based. This goes beyond schema field descriptions.

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 identifies the verb 'extract' and the resource 'selected statements into a new method'. It distinguishes itself from siblings like 'extract_variable' by specifying data flow analysis for parameters and return type.

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?

Provides explicit usage requirements ('Specify startLine/endLine range containing complete statements inside a method') and a two-step workflow ('Preview then Apply'). Does not explicitly contrast with alternative tools or state when not to use, but the workflow is helpful.

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