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

With no annotations, the description carries the full burden and discloses almost nothing beyond 'list': read-only behavior is only implied, and there is no mention of pagination, ordering, or whether the result includes references/placeholder assets touched by asset.replace_placeholder. For a mutation-free but potentially large enumeration, this leaves real gaps.

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 sentence is short and front-loaded, which is good, but the trailing spec citation '(§11.7)' is noise for an agent and consumes part of an already thin description. Sizing is appropriate; content density is low.

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?

The tool is structurally simple (one required string, no nested objects, no output schema), so it does not need much, but with zero annotations and no return-shape description the data contract is entirely undocumented. Adequate to identify the tool, insufficient to predict its results.

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?

There is one required parameter at 0% schema description coverage, and the description only says 'for a project', which implies projectId without stating its format or where it comes from. The description adds slightly more than the bare schema but does not properly compensate for the coverage gap.

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 ('List every asset') plus the scope ('for a project'), and the 'uploaded/generated' phrasing distinguishes it from asset.get, which returns a single asset. It stops short of naming siblings explicitly, so it's clear rather than differentiating.

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 word 'every' implies bulk enumeration, which implicitly tells the agent to use this instead of asset.get for single lookups, but no alternative or precondition is stated. An agent must infer that asset.get is the single-item counterpart.

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