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

Annotations already establish that this is a safe read-only operation. The description adds useful behavioral context beyond the annotations: results are ordered newest first, include state and publication, and each item is large so callers should page with limit and offset. It does not cover defaults, auth, or rate limits, but the annotation coverage lowers that burden.

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 sentences, front-loaded with purpose and then the key operational constraint. There is no wasted text, and the pagination guidance is concise and immediately actionable.

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 simple read-only list tool with annotations covering safety, the description gives the essential ordering and paging behavior. But with 0% schema description coverage, it should explain the search parameter and the required project/site identifiers more clearly. It is adequate but has clear gaps that could affect correct invocation.

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%, so the description must carry parameter meaning. It explains limit and offset well, including a suggested limit of 10 and the purpose of paging, but it never mentions the search parameter and does not clarify what projectId or siteId represent beyond the vague phrase "website's articles." Partial compensation leaves significant gaps.

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?

The description states a specific verb and resource: "List a website's articles." It also adds scope and return content (newest first, state and publication), making the purpose clear. It does not explicitly distinguish itself from siblings like get_article or list_article_keywords, so it stops short of a 5.

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?

The description implies the tool is for listing a website's articles and gives operational guidance to use limit and offset for paging because items are large. However, it does not say when to use this tool instead of alternatives like get_article, nor does it explain when to use search or when not to use the tool.

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