meta_ads_feeds_list

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

No annotations available, so description must carry disclosure burden. It states 'Read-only' and describes output fields, but omits pagination, error behavior, and rate limits. Adequate but not complete.

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?

Four compact sentences front-loaded with primary action, followed by return fields, read-only flag, and a diagnostic use case. No redundancy or padding.

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 exists, but description details the full return shape and even example enum values. Lacks pagination and result limits, but sufficient for a simple list operation.

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?

Input schema documents both parameters with 100% coverage, including account_id format and fallback. Description adds catalog context but no parameter-specific detail beyond schema. Baseline 3 applies.

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?

Clearly identifies verb (Lists) and resource (product feeds for a Product Catalog), and enumerates return fields. Distinguished from sibling feed-related tools by focusing on feed health listing.

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?

Explicit use case: 'Use this to audit feed health' and links to missing products in DPA. Does not mention exclusions or alternatives, but context is clear.

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