get_adsets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, making the safety profile clear. The description adds value by specifying the return envelope structure and included fields (identifiers, names, statuses, campaign IDs, daily budgets), and confirming it's for hierarchy inspection.

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?

Description is concisely written with key information front-loaded. It is a single paragraph that efficiently covers purpose, parameters, return format, and usage guidance without extraneous 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?

Given an output schema exists, the description sufficiently explains return envelope and data fields. Combined with usage guidelines and parameter descriptions, it provides complete context for using the tool correctly.

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?

Description explains parameters at a high level ('parent account or campaign ID, maximum result count, and JSON or Markdown response format'), adding context about response format options. However, the input schema already provides detailed descriptions, default values, and constraints, so the description's incremental contribution is limited.

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?

Description clearly states the tool retrieves ad sets beneath an account or campaign parent. It uses specific verb 'get' and resource 'ad sets', distinguishing it from sibling tools like get_campaigns and get_ads.

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?

Description explicitly says 'Use this to inspect the ad-set hierarchy for a known parent' and 'Do not use it for performance metrics or to create, edit, pause, or delete ad sets.' This provides clear when-to-use and when-not-to-use guidance, implicitly directing to sibling tools for other purposes.

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