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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about what the cards contain (real-brand visual merchandising ideas plus Findie creative insights) but says nothing about ordering, pagination behavior, or the shape of a returned card.

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 front-loaded sentence with no wasted phrasing; the verb and resource come first. The parenthetical introduces jargon ('Findie', 'brand-crushes') that is unexplained, slightly reducing clarity.

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 simple filtered list tool with one documented parameter, full annotation coverage, and no output schema, the description supplies enough about the content to call it correctly. Only the return-card structure and pagination are left implicit.

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 100% and the single limit parameter is fully documented in the schema with its default of 20 and maximum of 100. The description adds no meaning beyond that, so the baseline of 3 applies.

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 pairs a specific verb ('List') with a specific resource ('Sense2 editorial inspiration cards') and clarifies the domain via the parenthetical about brand-crushes and visual merchandising ideas. It does not, however, distinguish this tool from the similarly named sibling get_inspiration, leaving the near-duplicate pair ambiguous.

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 exclusions, and no pointer to an alternative such as get_inspiration or get_creative_branding_ideas. The agent must infer the use case purely from the content label 'inspiration cards'.

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