Get Ad Set Details

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safe, read-only behavior. The description confirms 'gets' but adds no additional behavioral details (e.g., return format, pagination). It does not contradict annotations.

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 with two sentences, clearly stating the purpose upfront. The 'Args' section repeats information already in the schema but is brief. No unnecessary content.

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?

The description provides basic purpose and one parameter hint. For a simple read-only tool with good annotations, it is minimally adequate. However, given many sibling tools, more context about return format or typical fields would improve completeness. Output schema is absent.

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 mentions 'adset_id' as 'Ad set ID', adding meaning to a parameter that lacks a schema description. However, it ignores 'response_format', which is documented in the schema. With 50% schema coverage, the description partially compensates but is incomplete.

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 states 'Gets detailed information about a specific ad set,' which is a clear verb+resource combination. However, it does not differentiate from sibling tools like meta_get_adset_insights, which could cause confusion about which tool to use for what purpose.

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 on when to use this tool versus alternatives, such as meta_get_adset_insights or meta_list_adsets. The description lacks context about prerequisites or appropriate scenarios for invocation.

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