bsl_definition

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

No annotations are present, so the description carries full responsibility. It only states the purpose and an example input, but does not disclose return format, side effects, or error behavior. For a likely read-only operation, this is insufficient.

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 extremely brief—one sentence and an example—which is efficient and front-loaded. However, it may be too sparse given the lack of other information.

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?

The tool has only one parameter and likely a simple output, but without seeing the output schema, the description leaves unclear what the agent will receive. There is no mention of what happens if the symbol is not found, and no details on the returned location structure. Given the availability of an output schema (per context), this may be adequate, but the description alone is 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 description gives a concrete example for full_name ('ОбщийМодуль.МойМодуль.ИмяФункции'), which clarifies the expected format. Since schema coverage is 0%, this example is valuable, but it is not a formal description and does not cover edge cases.

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 'Где объявлен символ' (where the symbol is declared), which clearly identifies the tool's function as locating a declaration. It also provides an example format for the full_name parameter. However, it doesn't explicitly differentiate from sibling tools like bsl_references, which might also find related locations.

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 is provided about when to use this tool versus alternatives like bsl_callers, bsl_callees, or bsl_references. The description does not mention any conditions or exclusions.

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