bsl_callees

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

No annotations are provided, and the description does not mention whether the operation is read-only, what the result format is (e.g., list of callees), or any permissions or side effects. The agent is left without essential behavioral context beyond the core action.

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 very brief and to the point. It includes a necessary example, which adds value without unnecessary verbosity. The structure is clean, though the lack of an explicit command verb in English might reduce universal clarity.

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 tool's simplicity, the description is minimal and lacks crucial context such as the expected return value (e.g., a list of call sites or function names) and any caveats. It is not sufficiently complete for an agent to fully anticipate the tool's behavior and output.

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 sole parameter 'full_name' has no schema description, but the description provides an example value ('ОбщийМодуль.МойМодуль.ИмяФункции'), which clarifies the expected format. However, it does not explicitly define what the parameter represents (the fully qualified name of the function) or any constraints.

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 'Кого вызывает функция' explicitly states that the tool returns the outgoing calls (callees) of a function. It clearly identifies the action (вызывает) and the resource (function), and contrasts with the sibling 'bsl_callers' by specifying 'outgoing calls'.

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 purpose is inherently clear from the name and description, but it does not explicitly instruct when to use this tool over 'bsl_callers' or other siblings. The distinction is implied rather than stated, which leaves some ambiguity for an agent.

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