meta_ads_pixels_get

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

Declares 'Read-only' which is clear for a get operation, and lists return fields. No annotations exist, so description covers behavioral traits adequately. Could mention authorization requirements, but not required for basic get.

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?

Two sentences: first defines purpose and returns, second gives usage context. No unnecessary words, front-loaded with critical information. Highly efficient.

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?

No output schema, so describing key return fields (id, name, code, etc.) provides needed completeness. Also includes use-case guidance. Lacks error handling or response format details, but sufficient for a simple 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 description coverage is 100%, so baseline 3. Description adds context that pixel_id comes from meta_ads_pixels_list, and account_id is optional with fallback, which aligns with schema but doesn't add significant new meaning beyond it.

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 a single Meta Pixel's detail record and lists specific fields returned. It distinguishes itself from siblings like meta_ads_pixels_list (single vs list) and meta_ads_pixels_stats (stats vs detail) by focusing on full detail.

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 tells when to use: 'Call this to verify pixel setup... before diagnosing conversion tracking issues or before relying on the pixel for audience rules.' Provides clear context and implies alternatives for other needs.

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