Get Ad Set Details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds no behavioral context beyond restating that it gets information. It does not disclose what data is returned, whether errors occur for invalid IDs, or how response_format affects output.

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 very short, front-loaded, and contains no filler. The Args list mostly mirrors the input schema, so it is concise but not information-dense.

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?

Because there is no output schema, the description should explain what 'detailed information' includes and how response_format changes the result. It does neither, nor does it mention required permissions or behavior for invalid ad set IDs, leaving the tool under-specified for an 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?

The description only restates adset_id as 'Ad set ID,' adding little meaning beyond the schema. It does not mention response_format at all, and with 50% schema description coverage plus no output schema, it fails to compensate for the gaps in parameter understanding.

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 and resource: it 'gets detailed information about a specific ad set,' which distinguishes it from listing, creating, updating, or deleting ad sets. However, it does not explicitly differentiate itself from sibling tools like meta_get_adset_insights, so the purpose is clear but not sharply separated.

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?

There is no guidance on when to use this tool versus alternatives such as meta_list_adsets, meta_get_adset_insights, or meta_get_ad. The phrase 'specific ad set' implies you need one ad set by ID, but no explicit usage context, exclusions, or alternative routing is provided.

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