get_signature_help

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

Discloses that coordinates are zero-based, which is critical behavioral information not fully captured in the schema. No annotations exist, so description carries burden well.

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?

Four lines, front-loaded purpose, structured usage and important note. No wasted 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?

Mentions output type but not format or error conditions. With no output schema, more detail on return value structure would improve completeness.

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 descriptions already document all three parameters with zero-based info (100% coverage). Description reiterates zero-based but adds no new semantics 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 gets method signatures at a position, which is specific. However, it does not explicitly differentiate from similar tools like get_method_at_position or get_hover_info, which could cause confusion.

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 usage context ('position on a method call or declaration') and a prerequisite ('Requires load_project to be called first'). Does not mention when not to use or alternatives.

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