Blog posts and care guides

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description usefully adds result ordering and the kind of content returned, but omits anything about pagination behavior or result-size limits beyond what the schema states. Adequate, moderate added value.

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?

Two short, front-loaded sentences with zero filler; the scope statement comes first and the usage routing second.

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?

With an output schema present and full annotation coverage, the description supplies exactly what is missing: what the tool lists, ordering, and how it fits into the read-one workflow. Nothing an agent needs to select or call it is absent.

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%, so page, limit, and query are already documented in the schema. The description only hints at query usage via advice examples and adds no new syntax or format guidance; baseline 3 is appropriate.

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 blog posts) plus the content domain (skin/hair care guides, routines, comparisons) and ordering (newest first). It also implicitly separates itself from the singular sibling ab_blog_post, which it names as the follow-up read tool.

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?

Explicitly says when to use it (advice-style questions) with two concrete example queries, and names the alternative workflow step ('find a matching post, then read it with ab_blog_post'). The agent knows both the trigger and the handoff.

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