x ads list media library

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

Annotations already communicate that the operation is read-only, idempotent, and non-destructive. The description adds meaningful behavioral context: Native X fields and pagination are preserved, and monetary fields ending in _micro are millionths of the account currency, which helps the agent interpret results correctly.

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 concise and front-loaded with the primary action. The second sentence adds useful output semantics without redundancy, though the phrasing 'in an ads account Native X fields' is slightly awkward and would benefit from a punctuation break.

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 list tool with a fully documented schema, annotations, and an output schema, the description covers the essential behavior: resource scope, field preservation, pagination, and monetary unit conventions. It lacks explicit usage guidance and sibling differentiation, but the core operational context is present.

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 the baseline is 3 even without additional parameter guidance. The description does not add input-specific meaning; the notes about pagination and _micro fields concern response interpretation rather than parameter semantics.

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 the operation: 'List the media library objects in an ads account', identifying both the verb and the resource. It is distinguishable from the sibling x_ads_get_media_library_item because this is explicitly a list operation, though it does not name or explicitly contrast that sibling.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention x_ads_get_media_library_item for single-item retrieval or explain when listing media library objects is appropriate, so the agent must infer usage context solely from the name and generic wording.

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