search_pages

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

With no annotations, the description carries behavior disclosure; it indicates a read-only, public-data search, which is a meaningful safety signal. However, it does not mention authentication requirements, pagination behavior, or rate-limit implications.

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 one clean sentence with the endpoint appended; no filler. It is appropriately short for a simple search operation.

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 simple read-only search with an output schema, the core invocation is clear and the required parameter is documented. The gap is in pagination parameters and guidance on when to use this versus page-by-ID tools.

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 coverage is 0%, so the description must compensate. It explains only query (the search term), leaving after and limit undocumented; after in particular is opaque without a pagination note.

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?

Description names a specific action (Search), the resource (public Facebook Pages), and the lookup semantics (by name/keyword), plus the underlying endpoint. This clearly differentiates it from get_page_info (by ID) and page content tools.

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?

It implies this tool is for discovery by keyword rather than fetching a known page, but it never states when to choose it over get_page_info or get_my_accounts. No exclusions or alternative routing are provided.

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