find_importers

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the matching logic (exact or suffix) which is valuable, but it does not state whether the operation is read-only, what the return format is, or any performance implications. This is a partial disclosure.

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 two sentences, front-loaded with the core purpose, followed by a concise explanation of matching behavior. There is no redundant text or filler; every word earns its place.

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 one-parameter tool, the description covers the essentials (purpose and matching behavior), but it lacks a distinction from the closely related sibling 'find_imports' and does not mention output format or side effects. Given the low complexity, it is slightly incomplete.

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?

The schema has 0% description coverage, so the description must compensate. It clarifies the 'target' parameter by stating it is a module path and gives examples ('os', 'fmt', 'utils.foo'), and explains the matching rules. This adds meaning beyond the bare schema definition.

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 states the tool's purpose clearly: 'Find files that import the given module/target.' It uses a specific verb and resource, and provides examples of matching patterns. However, it does not explicitly distinguish this from the sibling tool 'find_imports', which could cause confusion for an agent.

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 explains matching semantics (exact or suffix module paths) which implies when to use it, but it does not explicitly state when to prefer this over alternative tools like 'find_imports' or provide exclusions. There is no mention of use cases or limitations.

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