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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is well covered. The description usefully documents the available filter dimensions, but it does not mention pagination behavior, result size, ordering, or total-count behavior for a list operation.

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 definition is a single front-loaded sentence with no wasted prose. It states the resource and the filtering options immediately.

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 seven-parameter list tool with no output schema, the description covers most filter parameters but leaves pagination and result-shape expectations unstated. Annotations compensate for the safety profile, but pagination behavior remains a gap.

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 compensate. It does well by explaining website_id/website_uuid, collection_id/collection_uuid, and title_query as title-substring filtering, though it omits the page and per_page parameters.

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 clearly states the verb and resource: it lists articles and names the supported filters. It is understandable without opening the schema, though it does not explicitly differentiate from nearby siblings such as list_articles_comments or list_collections.

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 implies the tool is used to retrieve articles with optional filters, but it gives no explicit guidance on when to choose it over related tools like list_articles_comments or list_articles_links_counts. The optional filtering behavior is clear, but usage boundaries are only implied.

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