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. It discloses key behavioral traits: it returns full method source including signature, body, location, and line count. However, it does not mention potential errors (e.g., if the method doesn't exist), performance implications, or whether it requires a loaded solution, leaving some gaps in transparency.

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 front-loaded with the core purpose, followed by a usage example and output details. Every sentence adds value without redundancy, and it is appropriately sized for the tool's complexity, making it efficient and easy to parse.

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?

Given the tool's moderate complexity, no annotations, and no output schema, the description does a good job covering purpose, usage, and output format. However, it lacks details on error handling, prerequisites (e.g., needing a loaded solution), and performance, which could be important for an agent to use it correctly in all scenarios.

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 parameters thoroughly. The description adds minimal value beyond the schema by implying the parameters in the usage example but does not provide additional semantics, format details, or constraints. 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 tool's purpose with specific verbs ('Get the actual source code of a method') and resources ('by type and method name'), and distinguishes it from alternatives by noting it 'Eliminates need for file Read.' This explicitly differentiates it from sibling tools like 'get_file_overview' or general file reading operations.

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 clear context for when to use this tool (to get method source code without file reading) and includes a usage example. However, it does not explicitly state when not to use it or mention alternatives like 'get_method_source_batch' for batch operations, which is a minor gap.

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