search_pages_by_name

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

No annotations provided, so the description must carry the full burden. It mentions that access_token is optional and cached tokens may be used, which is useful. However, it lacks details on side effects, rate limits, pagination, or guarantees of idempotency, which are important for a searching 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?

The description is structured as a docstring with Args and Returns sections, making it easy to parse. It is relatively concise, though some sentences are longer than necessary. Overall efficient.

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 mentions an output schema (JSON response with matching pages) but does not elaborate on the structure or fields. Given the sibling tools and simplicity of the tool (3 params, no enums), the description provides a minimum viable context but leaves room for clarification on the return format and error handling.

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 0%, but the description adds meaning beyond the schema by explaining each parameter's format and optionality (e.g., account_id format act_XXXXXXXXX, access_token optional, search_term optional). This is basic and does not provide deeper semantics like allowed values or constraints.

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 for pages by name within an account, with a specific verb and resource. It distinguishes from siblings like get_account_pages (which likely lists all pages) by specifying the search by name aspect, though it could be more explicit about the return type.

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?

No guidance on when to use this tool versus alternatives such as get_account_pages or the general search tool. The description only states what it does but does not provide context for when to prefer it over siblings.

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