Get Meta Ad Set by ID

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context about returning an object with requested fields and lists common fields, but does not disclose additional behavioral traits beyond what annotations imply. The bar is lower due to rich 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 moderately sized and includes structured sections (Args, Returns, Examples). The 'Args' section largely duplicates the schema but adds practical examples. It is front-loaded with the main purpose, but could be slightly more concise by omitting redundant arg details.

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 low tool complexity, no output schema, and thorough annotations, the description adequately covers retrieval behavior. It specifies return format as an object with requested fields, and the examples cover common use cases.

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%, so baseline is 3. The description enhances understanding by providing a list of common fields (e.g., id, name, budget) and examples of use, adding value beyond the schema's brief descriptions.

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 tool retrieves detailed information about a specific Meta ad set. The verb 'retrieve' is specific, and the resource 'ad set' is well-defined. Among sibling tools like meta_ads_get_ad_by_id, this tool is distinctly focused on ad sets, making its purpose unambiguous.

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 description provides two concrete 'Use when' examples, such as retrieving targeting and budget for a specific ad set. However, it does not explicitly state when not to use this tool or mention alternative tools for different purposes, which would improve guidance.

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