Sarlavha bo'yicha kategoriya tavsiyasi

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable beyond-annotation context: authentication requirement ('Needs a logged-in session') and the exact return shape ('category ids with full path'). No contradiction with annotations.

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?

Four short sentences, each earning its place: what it does, the posting-form behavior it reproduces, the auth prerequisite, what it returns, and the natural next call. Front-loaded with the core action and 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?

For a simple one-parameter tool with no output schema, the description is fully sufficient: it states input semantics, auth requirement, return values, and the recommended follow-up call. An agent has everything needed to invoke it correctly and understand the result.

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 single parameter 'title' is already documented with an example. The description reinforces that it is an 'advert title' but does not add significant new meaning beyond the schema. This matches the baseline for high schema coverage.

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?

States a specific verb and resource: 'Suggest OLX categories for an advert title' with a precise reference to the olx.uz posting form suggestion behavior. This clearly distinguishes it from sibling tools like olx_list_categories and olx_get_category, especially by pointing the agent to olx_get_category for the next step.

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?

Provides clear usage context: needs a logged-in sessionchers, and directs the agent to follow up with olx_get_category(id) to see required parameters. It does not explicitly enumerate when-not-to-use alternatives, but the context is clear enough for an agent to select this tool over list/get category tools.

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