Get Ad Rule Details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds no behavioral context beyond restating that this is a read operation; it does not mention response format, error behavior, or any additional constraints.

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 short and front-loaded, with a clear one-line purpose followed by a compact Args section. It wastes no words, though the Args section lists only one of two parameters, which slightly reduces completeness without harming conciseness.

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?

For a simple, read-only, get-by-ID tool, the description plus annotations and schema is largely sufficient for an agent to invoke it correctly. Minor gaps remain: it does not describe what 'details' are returned and does not explicitly connect rule_id discovery to meta_list_ad_rules.

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 adds a minimal semantic for rule_id ('Ad rule ID'), but this is largely self-evident. It omits response_format entirely, although the schema already provides a full description for that parameter. With schema description coverage at 50%, the description only partially compensates for the missing parameter documentation.

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 a specific verb ('Gets details') and resource ('a specific automated ad rule'), making the tool's purpose immediately clear. It also distinguishes itself from sibling tools like meta_list_ad_rules, which list many rules, and meta_create_ad_rule/meta_delete_ad_rule, which mutate rules.

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 word 'specific' implies this tool is for retrieving one ad rule by ID, which hints at when to use it, but it does not explicitly mention alternatives or when not to use it. There is no direct guidance such as 'to list all ad rules, use meta_list_ad_rules instead.'

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