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

Annotations already establish read-only, idempotent, non-destructive, and non-open-world behavior, so the description does not need to repeat safety basics. It adds useful context by stating that results are links and that file tools run in the user's browser with files never uploaded, which is meaningful privacy and execution behavior.

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 front-loaded with the main action and stays compact while covering search scope, result type, and browser execution behavior. Each sentence adds useful information without repetition or 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?

Given the annotations and output schema, the description covers the important catalog scope, result format, and browser safety context well. It is only slightly incomplete because it does not explain the limit parameter or clarify routing against get_tool.

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?

The query parameter is already documented in the schema with examples, and the description adds relevant search-scope examples such as PDFs, images, text, calculators, and task presets. The limit parameter remains undocumented in both schema and description, so parameter coverage is only partially compensated.

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 gives a clear verb and resource: search 200+ free tools, and it enumerates the tool categories plus presets and clinics. It does not explicitly distinguish itself from siblings such as get_tool, though the search vs retrieve distinction is reasonably inferable.

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?

The description implies this is the discovery entry point by naming categories, task presets, and decision clinics, which helps an agent decide when to search. However, it gives no explicit when-to-use or when-not-to-use guidance relative to siblings like get_tool or list_clinics.

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