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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful catalog semantics: exclusions (Threads not included), manual-only handling by recent_posts, and daily_snapshot overlap, which go beyond structured data. It stops short of describing exact return shape, but no output schema exists either.

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 with the core action front-loaded ('List the source catalog'), followed by scoping details. Every clause (provenance, availability, manual-only, daily_snapshot, Threads exclusion) carries information; no filler.

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, no-output-schema listing tool, the description covers content, provenance, availability, and key exclusions well. Minor gap: it doesn't enumerate the returned fields explicitly, but it implies them sufficiently.

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. Nothing in the description contradicts or under-specifies an input surface that already has 100% schema coverage.

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 ('List') and resource ('source catalog') and clarifies the content dimension (categories, provenance, availability). The scope is easy to distinguish from recent_posts and daily_snapshot, though the phrase 'automatic availability' is slightly opaque.

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?

Usage is implied rather than stated; it explains how sources relate to recent_posts (manual-only not fetched) and daily_snapshot (some appear separately), but does not explicitly say 'use this to discover available sources before querying.' No direct when/when-not guidance for the tool itself.

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