Search KIT API operations

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

ReadOnlyHint is present, and the description adds useful behavioral context: the search covers the full catalog, matches multiple fields, and supports Russian text. It does not contradict the annotation, though it omits details about the return format or result pagination.

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 three sentences, front-loaded with the core purpose, then adds search semantics and workflow guidance. Every sentence earns its place with no redundant content.

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?

For a read-only search tool with no output schema, the description covers purpose, matching behavior, language support, and next steps. It lacks an explicit statement of the return shape, but the workflow with get_operation_schema compensates adequately.

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 coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining that the query parameter matches operationId, URL path, tag, and Russian summary/description, giving semantic meaning not present in the schema's syntax-focused description.

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 the verb ('Search') and resource ('full catalog of all 160 Yandex KIT API operations'), and specifies the matching fields (operationId, URL path, tag, Russian summary/description). This distinguishes it from sibling tools like kit_request (execution) and get_operation_schema (schema inspection).

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 description explicitly directs the agent to use get_operation_schema for parameter inspection and kit_request for execution, providing a clear workflow. It also advises that Russian keywords are supported, helping the agent craft effective search queries.

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