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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds ordering behavior ('ordered by date, modified, title, or relevance') and paging totals, which is useful beyond annotations. It lists return fields, which is somewhat redundant given an output schema exists, keeping it below 5.

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 dense sentence with the action and filter axes front-loaded, followed by the disambiguation clause. Every element earns its place, though listing the full return field set pushes length slightly beyond need given the output schema.

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 read-only search tool with annotations and an output schema, the description covers purpose, filters, ordering, and routing. The remaining gap is pagination semantics (page/page_size), which are undocumented everywhere and matter for an implementer pulling multiple result pages.

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% for all 7 params, so the description must compensate. It names the meaning of query, category, tag, and the order_by values, but leaves page and page_size entirely undocumented in both schema and description. Partial compensation warrants a mid score.

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 pair ('Search and list') and resource ('RetailMeNot blog posts'), enumerates the filter axes, and explicitly names the sibling retailmenot_blog_post as the tool for full articles. An agent can distinguish it from the category/tag listing siblings without opening a schema.

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?

Gives clear when-to-use context (filter by query, category slug, or tag slug) and an explicit alternative with its selection condition ('Use retailmenot_blog_post for the full article'). Nothing is left to inference on routing.

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