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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read only" restates what the agent already knows. The description adds nothing about result size, pagination, ordering, or which article states (drafts, published, rejected) are included — behavior beyond the annotations is undisclosed.

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 short sentences, action front-loaded, no padding. The second sentence is largely redundant with the readOnlyHint annotation, which keeps it from a 5.

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 parameters and rich annotations mean little prose is required, but there is no output schema and the description never indicates what an article record contains or how the list is paginated. For a list tool whose only job is returning data, that return-shape gap is the main omission.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The note that listing is scoped to the account is a small bonus, since there is no filter argument to convey that scope.

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 and resource ("List articles on your account"), so the basic action is unambiguous. However, with siblings like soclo_articles_checks, soclo_articles_destinations_list, soclo_posts_list and soclo_posts_drafts, it does nothing to say which article collection or state this returns, leaving the agent to guess from the name alone.

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?

"On your account" hints that results are implicitly scoped with no filtering arguments, but there is no statement of when to use this versus the many other article/posts listing siblings, nor any precondition. No exclusions or alternative routing are given.

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