Api assets list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only a vague hint that results are 'optimized' for the serializer context, without explaining pagination, filtering behaviour, response shape, or what 'optimized data' means for the caller.

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 text is one short sentence, but brevity here reflects under-specification rather than efficiency: the single sentence is an implementation aside and conveys no actionable information to an agent.

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?

A 25-parameter list tool with no output schema and no documentation of parameters, filtering semantics, or result shape needs a much richer description. The single implementation note is wholly inadequate for selecting and invoking the tool correctly.

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 are 25 parameters at 0% schema description coverage, and the description mentions none of them. Nothing explains the semantics of filters like asset_class, exclude_parents/exclude_children, filtering_labels, ordering, limit/offset, or max_pages, which an agent must supply correctly.

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 an internal implementation note ('Override the list method to inject optimized data into the serializer context') rather than a statement of what the tool does for a caller. Only the tool name implies that assets are listed; an agent reading the description alone learns nothing about the resource or the operation.

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, and no mention of alternatives such as the sibling object/retrieve, autocomplete, filter/detail, or export tools. The text describes a code-level detail, not usage conditions.

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