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

With no annotations and no behavioral description, the tool's effects, return format, authentication needs, or rate limits are completely undisclosed. The description adds zero value beyond the tool name.

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 in word count but this is under-specification, not effective brevity. A single vague noun phrase fails to convey essential information, making it below average.

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?

Given the tool's purpose of retrieving ad details, the description is severely incomplete. It does not specify what details are included, how the output is structured, or any constraints on the URL. No output schema exists, so the description carries the full burden, which it fails to meet.

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% because the single parameter 'url' includes 'The url of the ad'. Per the baseline for high schema coverage, a score of 3 is appropriate; the description adds no additional semantic meaning beyond the schema.

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 'Ad Details' is a noun phrase that simply restates the tool name. It lacks a specific verb (e.g., 'Get', 'Fetch') and does not clarify the resource or scope, making it indistinguishable from siblings like scrapecreators_get_ad or scrapecreators_ad_details.

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 about when to use this tool versus alternatives such as scrapecreators_search_ads or scrapecreators_company_ads. There are no prerequisites, exclusions, or context that would help an agent select this tool.

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