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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: result ordering favors the current satellite site then hub pages, and it signals that results are references to be opened with get_page rather than full content.

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, front-loaded with what is searched, then result ordering, then the next step, then a usage tip. Nothing is redundant with the schema and no sentence is 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?

With no output schema, the description carries the burden of explaining what comes back, and it does so indirectly by describing ordering and that results must be read via get_page. It stops short of describing result shape or how the limit interacts with result count, but the essentials for correct invocation are present.

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 all three parameters are already documented, including the site/all enum. The description still adds value by showing the intended query language and giving concrete Turkish query examples, and by explaining what "site" scope actually yields (this site plus top hub pages).

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 opens with a specific verb and an enumerated resource set: "Search published articles, buyer guides, solution pages, tools and design demos." This clearly distinguishes it from sibling tools that list one content type (list_design_demos, list_services) or fetch a single page (get_page).

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 explicit follow-up routing ("Use get_page to read a result") and explains the ordering behavior on satellite sites, which tells the agent what to expect from results. It does not, however, say when to prefer this over the list_* or get_frameworks siblings when browsing rather than searching.

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