meta_ads_ad_rules_get

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

With no annotations provided, the description must carry the behavioral disclosure burden. It states 'Read-only', which is a key safety trait, and lists the return fields, giving a clear picture of what the tool does. It does not mention error cases or auth, but for a read-only get operation, this is sufficient and adds value beyond the schema.

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 three sentences that are front-loaded with the primary action, followed by return value details and usage guidance. Every sentence provides useful information with no redundancy or filler.

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 the tool's simplicity (a get operation with two well-described parameters), the description is contextually complete. It explains the return values since there is no output schema, states the read-only nature, and gives usage context for a common workflow with meta_ads_ad_rules_update.

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 the baseline is 3. The description does not add extra semantic detail about parameters beyond what the schema already provides, but it doesn't need to because the schema is comprehensive.

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 it fetches the full detail record for a single Automated Rule, specifying the verb 'Fetches' and the resource. It also distinguishes itself from sibling tools like meta_ads_ad_rules_list by focusing on a single rule and from meta_ads_ad_rules_update by serving as a pre-update fetch.

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?

It explicitly instructs to call this before meta_ads_ad_rules_update to merge incremental changes instead of overwriting the whole spec. This provides clear when-to-use guidance and an explicit alternative, making it highly actionable for an agent.

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