get_meta_platform_id

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

Annotations already signal read-only (readOnlyHint=true) and open-world (openWorldHint=true) behavior. The description adds that it searches the live Facebook Ad Library and returns platform IDs, but does not disclose multiple-match behavior, failure modes, or rate limits. No contradiction with annotations.

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 front-loaded with the main purpose, but sentences 1 and 3 repeat nearly the same information ('Search for companies or brands...' and 'searches the Facebook Ad Library to find matching brands'). It could be tightened to two sentences.

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 one-parameter read-only search, the description explains the core output (platform IDs) and the integration point (before ad retrieval). However, with no output schema, it omits details about no-match results, multiple IDs per brand, and response format, leaving some uncertainty.

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 input schema has 0% description coverage for brand_names. The description mentions 'companies or brands' and 'matching brands,' but does not specify accepted format (string vs array), matching semantics (exact/fuzzy), or handling of multiple brands. It only partially compensates for missing schema documentation.

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 opens with a specific verb+resource: 'Search for companies or brands in the Meta Ad Library and return their platform IDs.' It clearly distinguishes from sibling get_meta_ads by framing this as the prerequisite ID lookup step ('before retrieving their 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 explicit context: 'Use this tool when you need to find a brand's Meta Platform ID before retrieving their ads.' It does not mention exclusions or alternatives, but the workflow positioning makes the target use case clear.

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