List banners

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds a small amount of context by naming the returned fields and hinting at the id format ("banner2"), but says nothing about whether all banners are returned, ordering, or pagination.

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?

Extremely short with no wasted words, and the resource is front-loaded. However, the terseness comes at the cost of missing the verb and any sentence structure that would make it self-explanatory.

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 zero-parameter list tool with no output schema, the description should at least confirm that it returns a collection of banners with the listed fields and whether it covers the whole shop. It gestures at the returned shape but leaves the return semantics (completeness, ordering, empty results) unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The field hints are useful mainly for constructing a subsequent get_banner call rather than for this tool's inputs.

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 a bare noun phrase, "Banners (id like \"banner2\", name, position)", which mostly restates the title "List banners" plus a field list. It does not itself state the action (list) or the scope (all banners in the shop), so an agent must rely on the name to infer purpose.

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?

No when-to-use guidance, no exclusions, and no pointer to the obvious sibling shoptet_get_banner for fetching a single banner by id. The listing intent is only implied by the tool name.

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