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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds value beyond them by enumerating what each result carries (titles, URLs, markdown URLs, descriptions) even though no output schema exists, though it omits the result-count cap of 20 and the default of 8.

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?

Two sentences, no filler: scope first, then the return contents and the follow-up call. Every clause is actionable.

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?

There is no output schema, and the description compensates by listing returned fields and pointing at get_page for follow-up. The only real gap is the undocumented limit/pagination behavior, which is minor for a simple keyword search.

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 0%, so the description carries the full burden, yet it only implies that query takes keywords. The limit parameter, its default of 8 and maximum of 20, and any guidance on result volume are never mentioned.

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) plus a precise resource and scope (every page on rankera.ai) and the matching mode (by keywords). It also names the sibling get_page as the read counterpart, so an agent can separate it from ask_question or list_services without opening any 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?

Gives an explicit next-step rule: use get_page to read a result, which establishes search-then-read workflow. It does not say when to prefer this over ask_question or the other lookup siblings, so exclusions are missing.

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