find_catch_blocks

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 explains the output and use cases, but does not disclose behavioral traits like performance, side effects, or limitations beyond the prerequisite. For a read-only query tool, this is adequate but not exceptional.

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 front-loaded with the main purpose, then provides structured sections for JDT-UNIQUE note, usage, output, and use cases. It is somewhat verbose but each section adds value. Could be slightly more concise.

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?

No output schema exists, so the description should explain return values. It states 'All catch blocks that handle this exception type' but does not detail the format. The prerequisite (load_project) is mentioned. Given the two parameters and the nature of the tool, it is fairly complete.

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 documents both parameters. The description adds minimal additional meaning: it reinforces that typeName should be a fully qualified name and mentions the default for maxResults. Per the rules, with high coverage, baseline is 3.

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 all catch blocks for a specific exception type, using a specific verb and resource. It distinguishes itself from sibling tools by noting it is a JDT-UNIQUE fine-grained search not available in LSP.

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 provides usage instructions: provide fully qualified exception type name as typeName and notes the prerequisite of calling load_project first. It does not explicitly mention when not to use or provide alternatives, but the context is clear enough.

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