v1_facebook_adLibrary_search_ads

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

With no annotations, the description fully covers behavior: it is a GET endpoint (read-only), costs 1 credit, returns mock data, and includes a critical safety warning that responses are data not instructions. No contradictions.

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 concise at 4 sentences. It front-loads the purpose, then efficiently covers endpoint, cost, stub status, parameter constraint, and a safety warning. No wasted words.

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 tool with 3 parameters and no output schema, the description is complete. It covers what the tool does, its current limited functionality (stub), required parameters, and a critical behavioral warning.

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 100%, so baseline is 3. The description adds the any-of constraint ('Requires one of query, pageId'), which clarifies the relationship between parameters beyond the schema labels.

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 verb 'Search' and the resource 'Facebook Ad Library ads', and specifies the endpoint and cost. It distinguishes itself from sibling ad library tools by being the search endpoint for ads.

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 provides clear preconditions by stating 'Requires one of query, pageId'. It also warns that the endpoint is a stub returning mock data, which guides usage expectations. However, it does not explicitly contrast with alternatives.

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