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 context beyond that: newest-first ordering, and that "pending" conflates drafts waiting, in-progress, and failed items — a non-obvious aggregation an agent would otherwise misread.

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?

A single dense sentence that front-loads the resource and ordering, then the status meanings. Slightly run-on with nested parentheticals, but nearly every clause earns its place.

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?

No output schema exists, and the description compensates by stating what each returned article carries (keyword, quality score, publication location, search performance). A read-only tool with annotations and a near-complete param breakdown is adequately covered; pagination behavior is the only unaddressed element.

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%, with org and limit documented in-schema; the status enum values carry no schema descriptions. The description compensates by defining all four enum values semantically, which is the gap the schema leaves and more than the baseline 3.

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 names the resource (articles) and its defining behavior (newest-first ordering, status-filtered listing), which separates it from single-article siblings like seovyn_get_article. The verb 'list' is only implied, but the status taxonomy makes the retrieval semantics unambiguous.

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?

Explaining that "pending" is the review queue tells the agent which status to pick for that intent, so usage is implied for the main scenarios. However, it never states when to prefer this over seovyn_get_article, seovyn_publish_queue, or seovyn_results, and there are no exclusions.

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