find_unused

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

No annotations provided, so description carries full burden. Discloses that only static imports are considered, that entry points are false positives, pagination behavior (default page size 200, offset), and return structure. Fully transparent beyond schema.

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?

Single well-structured paragraph front-loaded with core purpose, followed by usage advice, output format, pagination details, important notes, and error handling. Every sentence adds value, 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?

Given no output schema, description includes return shape and pagination. Covers special cases (entry points), error recovery, and static import limitation. Complete for a listing tool with pagination and error states.

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%, but description adds meaning: explains default limit value (200) and how offset works for pagination. Also shows output format with example. Adds value 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?

Clear verb ('List files that no other file imports') and resource ('orphan candidates for deletion'). Distinguishes from siblings by mentioning it uses the static import graph, avoiding manual cross-referencing.

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?

Explicitly states when to prefer this tool over alternatives ('Prefer this over manual Glob + Grep cross-referencing'), warns about entry points appearing unused, and provides error recovery steps ('On "Index not found" / "stale" error, call index_project, then retry').

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