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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that results are paginated and filterable, which is beyond the annotations, but it omits the non-obvious dual pagination mode (offset vs scan_cursor) that materially changes how the tool is driven.

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?

One front-loaded sentence with zero filler. It is efficient, though perhaps too terse for a six-parameter tool with a non-trivial cursor mode.

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?

Six all-optional parameters, no output schema, and a scan_cursor paging path that only makes sense in combination with filters. The schema documents each parameter individually, but the description leaves out what is returned and how the two pagination strategies relate, which is the main place an agent can go wrong.

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% and each parameter carries a description, so the schema does the heavy lifting. The description only restates the type and gallery filters and the existence of pagination, adding no semantics beyond the schema (e.g., it never mentions the multi-workspace requirement or the scan_cursor protocol).

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?

States a specific verb and resource ('Lists workspace assets') plus the two capabilities that matter (pagination, type/gallery filters). It does not differentiate itself from sibling list tools such as invoke_list_posts or invoke_list_campaigns, so an agent must infer that this one is for the asset library specifically.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. The only routing hint in the whole definition lives in the schema ('Optional ID from list_asset_galleries'), not the description, so nothing tells an agent to prefer this over other listing tools.

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