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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious trait beyond the structured data: returned preview URLs are signed and expire after five minutes, which matters for caching and downstream use. Pagination behavior for large workspaces is still undisclosed.

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?

A single sentence, zero filler, with the resource and the most surprising behavior (URL expiry) front-loaded. Nothing redundant with the annotations or title.

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?

An output schema exists, so return-shape explanation is not required, and the URL expiry note is a useful addition. However, for a paged list tool with two undocumented parameters, the description should at least indicate that results are paginated and that more calls may be needed.

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 0% and the description says nothing about limit or offset, so neither the pagination semantics nor the max page size of 100 is explained anywhere in prose. Only the generic mention of 'workspace media IDs' hints at the scope.

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 media IDs) and adds a distinguishing detail about temporary signed preview URLs. It is clear without needing the schema, though it does not explicitly contrast itself with sibling tools like list_posts or upload_media.

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 when-to-use guidance, no prerequisites, and no named alternative among the many siblings (e.g., list_posts, list_social_accounts). The agent must infer the retrieval context on its own.

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