find_method_references

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

No annotations provided, so description carries burden. It discloses zero-based coordinates and prerequisite load_project, but lacks details on side effects, performance, or return behavior. Adequate but not comprehensive.

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?

Description is well-structured with bullet points and clear sections. It front-loads the main purpose. Some redundancy (zero-based mentioned twice), but overall efficient.

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?

Covers usage context, prerequisite, and coordinate format. Missing output format description since no output schema is provided. Adequate for a tool with 4 parameters and clear purpose.

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%, so baseline is 3. Description adds zero-based coordinate emphasis and default maxResults (100), but these are already in schema. No additional meaning beyond 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?

The description clearly states the tool finds method reference expressions (Foo::bar lambda syntax). It distinguishes itself from siblings like find_references by specifying the lambda syntax and claiming 'JDT-UNIQUE', making its purpose distinct.

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 context on usage: position on a method or provide details, and requires load_project first. Mentions utility for functional programming and refactoring. However, does not explicitly state when not to use this tool vs alternatives like find_references.

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