get_super_method

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

No annotations are provided, so the description carries the full burden. It discloses the zero-based coordinate system and the need for prior project loading. While it doesn't explicitly state read-only nature or lack of side effects, the context of 'find' implies non-destructive behavior. Minor omission.

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 concise, using a clear structure with USAGE, OUTPUT, IMPORTANT, and Requires sections. Every sentence adds necessary information without wordiness.

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 simple tool with three required params, no output schema, and no annotations, the description is complete. It covers prerequisites, usage conditions, coordinate system, and output expectation. No gaps.

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 the schema already describes the three parameters. The description adds value by emphasizing 'Uses ZERO-BASED coordinates,' which reinforces correct interpretation beyond the schema's type definitions.

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: 'Find the method that this method overrides or implements.' It uses a specific verb and resource, and among siblings like 'find_implementations' and 'get_type_hierarchy', it uniquely identifies the superclass/interface method.

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 specifies when to use the tool: 'Position on a method that overrides/implements another' and notes the prerequisite 'Requires load_project to be called first.' This provides clear context and excludes inappropriate uses.

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