meta_ads_ad_rules_get

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

Declares read-only and enumerates return fields, adding value beyond the name. However, with no annotations, it could include details on authentication, rate limits, or error handling. Still provides sufficient transparency for a simple fetch.

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?

Three sentences: action+return, return fields, usage guidance. No redundancy, front-loaded with key info. Extremely concise.

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?

Enumerates return fields despite no output schema, and provides usage context. Could be improved by mentioning error scenarios or return format, but overall sufficient for a get tool.

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%, and the description adds minimal extra meaning (e.g., account_id fallback). Baseline 3 is appropriate as the schema already describes parameters adequately.

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, listing specific returned fields like evaluation_spec and execution_spec. It distinguishes from sibling tools (e.g., list vs single, read-only vs create/update/delete).

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?

Explicitly advises calling this before meta_ads_ad_rules_update to merge incremental changes, providing clear when-to-use context. Implicitly directs agents to use this for fetching details rather than listing.

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