Search pages

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

With no annotations, the description carries full burden. It discloses matching logic (ALL vs ANY) and output nature (compact summaries), adding value beyond structured data. No mention of rate limits or auth but acceptable for a read-like tool.

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 well-structured sentences, front-loaded with key criteria, no wasted words. Every sentence adds value: search scope, filter logic, return type, and follow-up actions.

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?

Adequately covers purpose, filter behavior, output, and next steps for an 8-parameter tool with no output schema. Lacks pagination details but offset/limit are schema-defined. Missing prerequisites but acceptable.

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?

Adds meaning beyond schema by explaining matching semantics (styles/assets must ALL match, industries ANY) and output nature (compact summaries). Schema covers most parameters, but limit lacks description; however, description compensates with context.

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 clearly states it searches full SaaS pages by multiple criteria (style, industry, page type, stack, free text), distinguishes from siblings like search_sections and get_page_details by specifying the return type and follow-up actions.

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?

Provides clear guidance on when to use (searching for pages) and how to narrow results (styles/assets ALL match, industries ANY), and suggests follow-up tools (get_page_details, get_screenshot). Lacks explicit when-not-to-use but context is strong.

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