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

No annotations are present, so the description carries full burden. It clearly declares the operation is a live read, indicating no mutation and no caching, and it details the complete set of returned attributes. It does not discuss auth or rate limits, but for a read tool the behavioral profile is well disclosed.

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 two sentences; the first is a long but purposeful enumeration of returned fields, the second is a usage directive. The density is justified for a tool that returns many distinct attributes, though it is not as tight as a simple list tool.

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 there is no output schema, the description itself documents the full return payload, the live vs cached distinction, and concrete use cases. An agent has enough to select and call the tool correctly without needing further references.

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%, and both parameters already have descriptive definitions (ad_set_id from adsap_list_ad_sets; ad_account_id as act_xxx). The description adds no param-specific details beyond the schema, so the baseline of 3 applies.

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 and resource: 'Read ONE ad set in full, live from Meta.' It enumerates the exact fields returned and contrasts itself with adsap_list_ad_sets' cached row, so it is unambiguously distinct from siblings.

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 explicitly states when to use this tool: 'Use it when adsap_list_ad_sets' cached row is not enough,' and lists three concrete scenarios: replicating an ad set, auditing targeting, or answering 'who exactly does this ad set target?'. This is strong when-vs-alternative guidance.

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