roslyn:get_method_overloads

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

Beyond the basic operation, it notes the important behavioral detail that coordinates are zero-based. Without annotations, this disclosure adds value. Does not cover safety or permissions, but the read-only nature is implied.

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: purpose, return value, usage hint with critical coordinate warning. No unnecessary words, front-loaded information.

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?

Fully describes what the tool does, what it returns, and key usage details. For a simple tool with no output schema, this is complete and sufficient for an agent to use correctly.

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% and descriptions are already explicit (e.g., 'Zero-based line number'). The description reiterates the zero-based constraint but adds no new semantic meaning beyond the schema.

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?

Clearly states it retrieves all overloads of a method and returns signatures with parameter details. Differentiates from siblings like get_method_signature by focusing on overloads, and includes usage context.

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 states 'Use when you need to choose between overloads', providing a clear context for use. Does not include when-not or alternatives, but the positive use case is well defined.

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