roslyn:implement_missing_members

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

No annotations are provided, so description must fully disclose behavior. It mentions zero-based coordinates and output of stub code, but does not cover edge cases (e.g., no missing members), side effects, or permission requirements for a code modification 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?

Three concise sentences with clear front-loading: purpose, usage, and important coordinate detail. No unnecessary words.

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 adequate for a code generation tool but lacks details on output format, error handling, or behavior when no missing members exist. No output schema to supplement.

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 covers all 4 parameters (100%), so baseline is 3. Description adds value by emphasizing zero-based coordinates and implicitly linking cursor position to line/column parameters, reinforcing usage.

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?

Description clearly states 'Generate stub implementations for interface/abstract members,' which is a specific verb+resource. It distinguishes from sibling 'get_missing_members' (retrieval vs. generation).

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 class declaration implementing interface or extending abstract class, providing clear usage context. However, it does not mention when not to use or point to alternative tools.

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