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

With no annotations, the description does substantial disclosure: parent_id results come instantly from a snapshot, query mode makes one live request, counts are live, and results are sorted largest first. It also documents the response shape, though it does not cover error behavior, permissions, or rate limits.

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 dense and front-loaded, opening with the tool's purpose and then covering each mode and the result shape. Given the absence of an output schema, including the result format earns its place rather than being redundant.

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 three-parameter browse tool with no output schema and no annotations, the description covers the missing context well: all operating modes, data freshness trade-offs, ordering, and the returned fields. An agent has enough information to invoke it correctly and interpret results.

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 the baseline is 3, but the description adds meaningful semantics beyond the schema: no arguments returns 19 top-level categories, parent_id lists sub-categories, and query returns categories with live offer counts ordered largest first. It also explains that path is a full Polish name trail.

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 a specific resource and goal: finding a category_id for olx_search. It distinguishes all three modes of operation and names the sibling tool it feeds into, so an agent can identify its role without opening the schema.

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 explicitly explains when to call without arguments, with parent_id, and with query, including why the query mode is useful: it is the quickest way to pick a category for a search term. This gives clear mode-selection guidance and ties the tool to olx_search.

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