apple_list_assets

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool follows every page, which is important pagination behavior, but it does not state permissions, ordering, rate limits, or the response shape.

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 a single front-loaded sentence with no wasted words. The core listing behavior comes first, followed by the use-case note.

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 five-parameter tool with no annotations, no output schema, and zero schema description coverage, the description provides the essential purpose and pagination behavior but leaves major gaps around filters and return details. It is minimally adequate but not complete.

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 0%, so the description must compensate for all five parameters. It only indirectly maps mediaType (image or video) and assetLibraryId (App Asset Library); it says nothing about state, category, or referenceName, nor about the enum values or filtering behavior.

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 and resource: list all image or video assets in an App Asset Library. It distinguishes this from sibling operations like apple_get_asset (single asset) and apple_list_asset_placements (placements rather than assets) by scoping the result to all assets and noting automatic pagination.

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?

It gives clear usage context: reuse files and find interrupted uploads. However, it does not name alternatives or state when not to use this tool, such as when to prefer apple_get_asset for a single asset.

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