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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination via cursor/limit, default page size, or what "optional thumbnails" costs in payload terms.

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 shortness here is under-specification rather than efficiency; the two fragments carry almost no information. Nothing is front-loaded because there is effectively no content to front-load.

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 10-parameter filtering/pagination tool with no output schema and no parameter descriptions, the description is far too thin. An agent cannot infer filter semantics, pagination behavior, or result shape from "Owned assets; optional thumbnails."

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% across 10 parameters, including three enums (type, source, status) and a UUID `project` filter, yet the description explains none of them. The only hint is "optional thumbnails," which loosely maps to include_thumbnails and leaves the other nine parameters undocumented in both places.

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?

"Owned assets; optional thumbnails" is a noun fragment with no verb, so it only indirectly conveys that this lists assets. It does not distinguish the tool from siblings like assets_get, assets_delete, assets_import, or assets_upload_url, which all operate on the same resource.

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 statement of when to use this versus assets_get (single asset fetch) or the many other list tools. The word "Owned" faintly implies a scoping rule, but with a `source` enum that includes imported and ai_generated, that implication is unclear rather than helpful.

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