Find callers of a symbol

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

No annotations are provided, so the description must fully disclose behavior. It mentions the use of the real TypeScript type checker and correct cross-file handling, which is helpful, but it omits details about return format, error cases, or performance costs, leaving some ambiguity.

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?

Two sentences, both earning their place. The primary action is front-loaded, and the second sentence provides a necessary usage hint without redundancy. No filler words or circular phrasing.

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 tool with no output schema, the description adequately conveys the outcome (list of callers) and the prerequisite workflow. Given the moderate complexity, it is sufficiently complete for an agent to invoke correctly, though it could mention the exact return structure without harming the score.

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% with clear parameter descriptions, so the baseline is 3. The description adds practical context by emphasizing that symbol_id must come from find_definition, which reinforces the schema and aids correct invocation, but it does not add new meaning beyond that.

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 action with a specific verb and resource: 'Find every function/method that calls a given symbol.' It also distinguishes the tool from the sibling find_callees (which finds the opposite direction) and the cross-file correctness adds meaningful context.

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 instructs to use find_definition first to obtain the exact symbol id, providing a clear prerequisite. It implies superiority over text-matching searches but does not list when-not-to-use alternatives. The guidance is practical and actionable.

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