getAdSetDetails

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' indicates a read-only operation, and the named fields suggest return content, but the description does not disclose response shape, error behavior, or access requirements.

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 a single front-loaded sentence: verb, resource, and example fields. There is no unnecessary wording or filler, making it easy to parse quickly.

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 one-parameter read tool, the core invocation is clear. However, with no output schema and no mention of alternatives, the response structure remains ambiguous and the tool is not explicitly positioned relative to siblings like getAdSets.

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 single parameter adSetId is already fully described in the input schema, so the description adds no new parameter-level detail. It does provide mild context that the ID is for fetching extended ad set details, but no format or source semantics.

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 clearly states the verb ('get'), resource ('ad set details'), and the word 'extended' with example fields. This distinguishes it from list-oriented siblings like getAdSets, though it does not explicitly name that sibling.

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?

The phrase 'extended ad set details' implies this is for deeper inspection of a single ad set, but the description does not explicitly state when to choose this tool over getAdSets or other detail tools. Usage context is inferred rather than explicit.

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