sharplens-mcp

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it specifies the output format ('List of missing members with exact signatures ready to copy'), the coordinate system requirement ('Uses ZERO-BASED coordinates'), and the positioning requirement. It doesn't mention error conditions or performance characteristics, but provides substantial operational context.

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 perfectly structured with clear sections: purpose statement, usage instructions, output description, and important technical note. Every sentence earns its place with zero wasted words, and the most critical information (what the tool does) is front-loaded.

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 tool with no annotations and no output schema, the description provides excellent coverage of what the tool does, when to use it, and important technical constraints. The main gap is the lack of information about what happens with invalid inputs or error conditions, but otherwise it's quite complete for a discovery/analysis 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 description coverage is 100%, so the schema already documents all three parameters. The description adds the important contextual note about 'ZERO-BASED coordinates' which helps interpret the line/column parameters, but doesn't provide additional syntax or format details beyond what the schema provides. This meets the baseline for high schema coverage.

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 specific action ('Get all interface and abstract members that must be implemented for a type') with the exact resource ('missing members with exact signatures ready to copy'). It distinguishes from sibling tools like 'roslyn:implement_missing_members' by focusing on discovery rather than implementation.

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 provides explicit usage instructions: 'Position on a class that implements interfaces or extends abstract classes' and 'Use before implementing interfaces.' This gives clear context for when to use this tool versus alternatives like 'roslyn:implement_missing_members' which would be used after this discovery phase.

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