app_asset_libraries_images_get_to_many_relationship

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

No annotations are provided, so the description carries the full burden. The 'GET' prefix weakly implies a read-only fetch, but nothing is said about pagination behavior, relationship-vs-resource payload shape, or permissions on the asset library. For an unannotated tool this is a substantial gap.

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?

It is short but wastes its only sentence on a verbatim duplicate of the same endpoint string in parentheses. There is no front-loaded explanation of what the call returns, so brevity here is under-specification rather than concision.

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?

With no annotations, no output schema, and a confusingly similar sibling pair (relationship vs related), the description should explain the relationship-endpoint semantics. The endpoint path gives only minimal orientation and leaves the agent guessing about what the call actually returns.

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 100% with documented 'id' and 'limit' fields, so the schema already does the work; per the baseline rule this scores 3. The description itself contributes nothing about pagination via limit or how id must resolve to an asset library.

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 is only the raw endpoint 'GET /v1/appAssetLibraries/{id}/relationships/images', repeated verbatim in parentheses. It restates the tool name rather than explaining in plain language that it lists the images in an App Asset Library; the agent gets no verb-plus-resource statement beyond decoding the URL.

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, no prerequisites, and no mention of the closely-named sibling app_asset_libraries_images_get_to_many_related or videos_get_to_many_relationship, which are equally plausible choices. Nothing helps the agent choose among near-identical siblings.

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