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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral detail beyond them: a hard cap of ~10 results, bukaez.com links in the output, and the restriction to public adult content. It does not describe failure/empty-result behavior, but that gap is minor given the annotation coverage.

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?

Three tight sentences with the purpose, result shape, pagination, and content restriction front-loaded ahead of lower-priority examples. Nothing is redundant, though the inline example terms occupy space that could be trimmed.

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 usefully compensates by disclosing result count and link format, and it flags the public/adult-only constraint. The type and lang filters are left entirely to the schema, which is acceptable at 100% coverage.

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%, so all four parameters (query, lang, page, type) are documented in the schema itself. The description only reinforces query examples and page usage; it adds nothing about lang or the type filter, so the baseline 3 applies.

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 ("Search") and concrete resources (public posts, bukaes, communities) with example queries, so an agent immediately knows the domain. It does not explicitly differentiate itself from siblings bukaez_read or bukaez_about, but search-vs-fetch is inherently separable.

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?

Gives a usage hint for pagination ("Use page 2–3 for more") and states the content eligibility rule ("Only public content from adults is searchable"), which tells the agent when results will be empty. However, there is no explicit routing guidance such as when to prefer bukaez_read to fetch a specific result instead of searching.

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