Search Meta Pages by Name

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

Annotations already indicate readOnly, non-destructive, and idempotent behavior. The description adds crucial details about client-side filtering and the lack of server-side name filter, going beyond annotations. It doesn't mention performance implications or output structure, but the added context is valuable.

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 concise (three sentences plus Args line) and front-loaded with the action. Every sentence adds value: what it does, how it works, and a key limitation. No unnecessary information.

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 tool, the description covers the main behavior and parameter. It could mention the return format (e.g., list of page objects) or potential performance concerns for large accounts, but it is generally adequate.

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 schema has 0% description coverage, so the description carries full burden. It clearly explains that search_term is a substring to match against page name or username, adding essential meaning beyond the type and minLength constraint.

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 the tool searches user's pages by case-insensitive substring of name or username, using an active verb and specific resource, and distinguishes from siblings like meta_ads_get_account_pages which retrieves all pages without filtering.

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 explains the internal mechanism (client-side filtering after fetching all pages) and the Graph API limitation, implying when this tool is appropriate. However, it does not explicitly state alternatives or when not to use it, though context from siblings is available.

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