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

With no annotations, the description must carry behavioral load. It usefully discloses the default implicit filtering (blog-only) that governs the whole result set, but says nothing about read-only safety, result size/pagination, or the limit cap behavior beyond what the schema already states.

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 with zero filler; the default-scope constraint is front-loaded before the content_kind escape hatch, which is exactly the ordering an agent needs.

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 listing tool with no output schema, the description never characterizes what comes back (item shape, ordering, pagination) and drops the collection_id filter that exists in the schema. Filtering scope is well covered, but the return-side picture 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 coverage is 67% and the description restates the content_kind semantics already documented in the schema, adding no new syntax or interaction detail. It does mention language/status and content_kind but omits collection_id and limit semantics entirely.

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 (list) and resource (articles in a site), plus the key scope detail that the default is BLOG-only content. However, it never distinguishes itself from the closest sibling, Search_Articles, which an agent must choose between for the same resource.

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 context on how to drive the tool's main branch point: default blog listing, content_kind='help' for KB articles, 'all' for both. It does not state when to prefer this over Search_Articles or Read_Article, so it stops short of full alternative guidance.

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