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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds domain-level behavior by distinguishing official/independent origins and manual versus automatic collectors, but says nothing about pagination, rate limits, or permission requirements.

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 tight sentences with the primary purpose front-loaded and no filler. The second sentence is slightly tangential to the listing action but still earns its place by clarifying dataset provenance.

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?

An output schema exists, so the description arguably over-explains return fields while omitting usage guidance and any explanation of its two filter parameters. For a simple read-only list tool this is adequate but leaves real gaps around filtering.

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% and both parameters (product, language) are undocumented enums in the description. The description nowhere explains that results can be scoped by product or language, or what the enum values mean, so it fails to compensate for the coverage gap.

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 ('public source URLs') and enumerates the fields surfaced (origin, collection state, last successful collection, item counts), so an agent knows exactly what it returns. It does not, however, contrast itself with siblings like botclaw_get_catalog or botclaw_get_item, which also deal with source-level metadata.

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?

There is no explicit guidance on when to call this versus alternatives, nor any prerequisite or exclusion. The only contextual note ('Manual sources are editorially reviewed; they are not automatic collectors') describes data semantics, not usage conditions.

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