find_callees

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

Without annotations, the description bears full behavioral burden. It does not disclose whether callee search is direct or recursive, nor does it describe output format, performance implications, or side effects. The presence of 'max_results' suggests potential large result sets, but this is not clarified.

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 a single concise sentence with no wasted words. It is front-loaded with the core purpose.

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 and no annotations, the description should provide more context about return values, scope, or limitations. It lacks details that would help an agent understand what to expect or how to interpret results.

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 both parameters are already described in the schema. The description adds no additional semantic information beyond what the schema provides for 'function_name' and 'max_results'.

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 'Find all functions called by a specific function' clearly states the verb and resource. It distinguishes from siblings like 'find_callers' and 'find_call_chain' by implying direction (callees vs callers). However, it could be slightly more specific by noting the scope (e.g., in the codebase).

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?

No guidance on when to use this tool versus alternatives. The description does not mention when not to use it, nor does it reference sibling tools like find_callers or find_call_chain for comparison.

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