search_syntax

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly states the key constraint: 'Даёт только строку списка' (gives only a list line), and points to get_syntax for the full syntax. It does not mention read-only status or matching semantics, but for a search tool the limited output is the main behavioral trait and it is covered.

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 short sentences front-load the purpose and immediately disclose the output limitation and the alternative for richer results. Every sentence earns its place with no filler.

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 search purpose, a fully documented schema, and an output schema, the description is largely complete for calling the tool correctly. A minor gap is the absence of explicit guidance about when not to use it versus config-oriented search tools, but the 'платформы 1С' qualifier mostly resolves this.

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%, and the schema already documents query, kind, limit, and config with helpful guidance. The tool description adds no parameter-specific detail beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb with a clear resource: 'Найти метод, свойство или объект платформы 1С' (find a method, property, or object of the 1C platform). It also distinguishes itself from get_syntax by stating that signature, parameters, context availability, version, and replacement recipe live in the sibling tool.

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?

It gives an explicit routing rule: for detailed syntax information, use `get_syntax` on the found name. It does not explicitly list exclusions for other search siblings like search_objects or search_procedures, but the phrase 'платформы 1С' narrows the scope to platform entities rather than configuration objects.

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