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

The description goes far beyond the provided annotations by detailing internal operational behaviors. It explains that media is downloaded and details specific logic regarding expired links—they are refetched once, which incurs a specific cost ('one Ad Spy lookup').

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 definition is highly dense but maximizes information density; every sentence conveys critical operational detail. It avoids unnecessary jargon while clearly laying out constraints and consequences.

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 complexity of a vault-saving mechanism, this is extremely complete. It covers authentication needs, storage limits, state management (polling), and resource costs, leaving no ambiguity for the agent.

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?

Since the schema description coverage is 100%, the baseline score is 3. However, the description adds useful semantic context by clarifying that 'creative_ids' refers to the internal Sonar ID, not the external Meta Ad ID, which is a vital distinction.

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 uses the specific term 'save Meta ads to the account's private vault,' clearly identifying the action and the resource. It distinguishes this function from other related functions by focusing on the persistence and freezing of the ad details and media within Sonar's storage.

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 comprehensive usage guidelines, including plan requirements (Indie or Agency), necessary permissions (authorized account/API key), and operational flow. Crucially, it outlines the limitation behavior, reporting 'over_limit,' and instructs the user to poll 'sonar_ad_spy_vault' for status.

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