find_catch_blocks

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

With no annotations, description carries the burden. It states the tool finds catch blocks and requires load_project, but does not disclose performance characteristics, limits (e.g., maxResults default), or error behavior. Adequate but could be more transparent.

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?

Every sentence adds value: purpose, uniqueness note, usage, output, use cases, prerequisite. No redundancy. Well segmented and front-loaded.

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 2-param tool with no output schema, description covers purpose, usage, and prerequisite. Mentions output type but lacks details on format or pagination. Good overall.

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?

Input schema has 100% description coverage, so description adds little beyond echoing the param purpose. Baseline 3 is appropriate since schema already explains parameters well.

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?

Description clearly states 'Find all catch blocks for an exception type', with a specific verb and resource. It distinguishes from sibling tools like 'find_references' and 'find_annotation_usages' by targeting catch blocks, and the JDT-UNIQUE note highlights its unique value.

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?

Description provides a prerequisite ('Requires load_project to be called first') and context ('JDT-UNIQUE: not available in LSP'). It does not explicitly compare to alternatives or state when not to use, but the usage direction is clear.

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