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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that: it explains that active posts are visible on the blog and inactive are not, and it discloses the auth requirement (Cotlet API key with access to this app), which annotations do not convey.

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?

The content is front-loaded with the return shape and purpose, and every sentence carries usable information. It is slightly dense and repetitive in restating the blog/post ID handoffs, but there is no filler.

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 no output schema, the description compensates well by enumerating the returned fields and the active/inactive semantics, and it includes the auth requirement. It could still note pagination/ordering behavior for the 1-100 limit, but nothing an agent needs to call it correctly is missing.

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 both parameters are already documented, giving a baseline of 3. The description clarifies what blog_id represents (returned for create_blog_post) and implicitly what the returned post_id is, but adds nothing about the limit parameter or its pagination effect.

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 (lists) and resource (posts of one blog) up front, and enumerates the returned fields (title, URL path, categories, active). It also distinguishes itself from siblings by naming activate_blog_post and create_blog_post and the ID handoffs between them, so an agent can separate it from the other systeme-io blog tools.

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?

It gives clear workflow context: the post_id returned feeds activate_blog_post and the blog_id feeds create_blog_post. However it never states when to use this list tool versus any alternative listing approach, and there are no exclusions, so it stops short of the explicit when/when-not routing a 5 requires.

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