gograph_callers

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

Description adds substantial context beyond annotations: declares it's 100% local, read-only, no side effects, no auth needed, no rate limits, zero destructive modifications. This complements annotations (readOnlyHint, idempotentHint) with concrete behavioral details.

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?

Description is well-organized with clear sections (BEHAVIOR & SAFETY, USAGE GUIDELINES, COMPLETENESS). Every sentence is purposeful and concise, no extraneous text.

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 the simple tool (one parameter, no output schema, rich annotations), the description covers all essential aspects: purpose, usage, behavior, required parameter, and return value structure. It is complete for effective tool selection and invocation.

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_description_coverage is 100%, so baseline is 3. Description mentions the 'function' parameter requirement and gives an example, adding slight extra value but not deep semantic context 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?

The description clearly states it finds and lists all functions/methods that call a specified target function. It uses specific verb+resource and distinguishes from sibling tool gograph_callees.

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 use (impact analysis, tracing call hierarchies, identifying API consumers) and when not to (use gograph_callees for downstream callees). Provides clear guidance.

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