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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read only' merely restates structured data. The only net-new disclosure is that each issue carries a status field; nothing about ordering, volume, pagination, or account scoping is provided.

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 very short sentences with no filler, front-loading the returned content. It is terse to the point of under-specification, but nothing is wasted or buried.

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 zero-parameter read-only list tool with full annotation coverage, the description is minimally adequate, but with no output schema an agent gets no sense of result volume, ordering, or whether issues are scoped to a connected account. A short clause on that would close the 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?

The tool takes zero parameters, so the baseline is 4: there is nothing for the description to disambiguate. No parameter-level value could be added here.

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 fragment 'All issues with their status' plus the tool name convey that this lists newsletter issues, but the description itself supplies no verb and does not distinguish it from the singular soclo_newsletter_issue sibling that presumably fetches one issue. The purpose is inferable but not stated crisply.

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?

'Read only' signals safety, not usage. There is no statement of when to call this versus soclo_newsletter_issue (single-item fetch) or soclo_newsletter_overview, and no prerequisites or exclusions are given.

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