Blog posts and buying guides

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds ordering ('newest first') and that entries include links, but does not disclose that the schema default category='buying_guide' means a bare call returns only buying guides, not all posts. Useful but incomplete context beyond the annotations.

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 tight sentences: the capability first, then the usage routing. Nothing is padded, though the trailing fragment about mk_blog_comments reads slightly like an afterthought rather than being fully integrated.

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, return values need not be explained, and the annotations carry the safety profile; the description covers purpose, ordering and usage routing. The main omission is flagging that the default category filters results to buying guides only, which an agent could misread as 'all posts'.

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 category are all documented in the schema, including the enum values with Persian glosses. The description adds nothing about parameter behavior (e.g. that category defaults to buying_guide), so the baseline 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?

States a specific verb and resource (list blog posts), enumerates the content types (buying guides, comparisons, how-tos), and adds ordering ('newest first, with links'). It also names the sibling it is not (mk_blog_comments) so the agent can separate it from the reader-question tool without opening either 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?

Explicitly states when to use it ('when the user asks which product type to choose or how to use a gadget') and what to do with the result ('point them to the matching guide'). It also routes the adjacent need (readers' questions answered by the store) to mk_blog_comments, giving a clear alternative.

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