Search Buildin and fetch top results as Markdown

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

No annotations are provided, so the description carries the full burden. It discloses the rate-limitation behavior via the limit default and return structure, but does not mention error handling, authentication requirements, or what happens when a page fetch fails. The transparency is adequate but not thorough.

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, front-loaded with the core action. No redundant or extraneous information. Every sentence contributes to understanding the tool's function.

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?

The description explains the return format and limit's purpose, which is helpful given no output schema. However, it fails to mention the max_depth parameter, leaving a gap in completeness for a tool with three parameters.

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 baseline is 3. The description adds a rate-limit context for the limit parameter but does not explain max_depth. For query, it merely restates 'Search query.' which is already in schema. Thus, minimal additional meaning beyond the schema.

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 specifies the action: search and fetch page content as Markdown. It distinguishes from siblings like buildin_search (which likely only returns search results) and buildin_get_page_markdown (single page fetch) by combining both steps and returning an array with id, title, url, markdown.

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 mentions the limit defaults to 3 to stay within rate limits, providing a usage hint. However, it does not explicitly state when to use this tool versus alternatives (e.g., buildin_search then buildin_get_page_markdown separately), nor does it provide exclusions or prerequisites.

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