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

No annotations are present, so the description must disclose behavior. It fails to mention return format, credit costs, pagination, or side effects. The only behavioral hint (get_ad_details costs 25 credits) appears in the schema, not the description.

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?

'Company Ads' is under-specification rather than conciseness. A two-word phrase cannot convey the semantic load of an 8-parameter tool, and there is no structure to guide an agent's reading.

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 tool with 8 optional parameters, no output schema, and no annotations, the description is drastically incomplete. It does not explain the tool's purpose, usage context, or relationship to sibling ad tools, making it nearly impossible to select and invoke correctly.

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 100%, with all 8 parameters documented (topic, cursor, domain, region, dates, advertiser_id, get_ad_details). The description adds no parameter-level meaning, but the high schema coverage meets the baseline of 3.

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 'Company Ads' is a noun phrase identifying a resource but lacks a verb indicating the action (get, search, list). It does not distinguish among sibling tools like scrapecreators_company_ads or scrapecreators_advertiser_search, leaving the operation ambiguous.

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 is provided on when to use this tool versus alternatives. With many ad-related siblings (e.g., scrapecreators_company_ads, scrapecreators_ad_details_get, scrapecreators_search_ads), the description offers no context, prerequisites, or selection criteria.

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