Advanced Search

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: 'Supports bounded all_pages; every page counts against the API quota,' disclosing quota consumption and bounded pagination. This is valuable rate-limit and execution behavior not otherwise stated.

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 very short (three sentences) and front-loads the quota note, but the first sentence 'Advanced Search' merely repeats the title and does not earn its place. 'Reads community data' is vague, while the quota sentence is the only genuinely informative one. It is concise but inefficient in content allocation.

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?

For a 9-parameter search tool with nested filters, multiple search types, and many sibling search tools, the description is insufficient. It does not explain what entity types are searched, when to choose this tool over specialized alternatives, or what the bounded all_pages return behavior implies beyond quota. Annotations cover safety, but routing and scope remain unclear.

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 parameters are already well documented in the input schema, including all_pages, max_items, account, and filters. The description adds no additional parameter meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 says 'Advanced Search. Reads community data,' which states a verb and resource but remains very broad. It does not specify that it searches across multiple entity types (posts, members, comments, etc.) and does not distinguish itself from sibling search tools like search_member or search_paywalls. The purpose is implied but vague.

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?

There is no guidance on when to use this generic search versus the many sibling search tools (search_member, search_paywalls, search_locations). The only usage-related note is about all_pages quota, which is about behavior, not context selection. An agent is left to infer usage conditions from the schema alone.

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