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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description does not contradict it. The description adds genuine value by disclosing the cost model ('1 credit') and the payload shape (text, images, polls, likes, comments). It omits pagination behavior despite cursor/continuationToken parameters, and says nothing about volume limits or rate behavior for an open-world scraper.

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 sentence plus a cost tag, front-loaded with the resource and with zero filler. It is arguably over-compressed — a fragment rather than a sentence — but nothing is wasted and the highest-value facts (what it returns, what it costs) come first.

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?

With no output schema, the description carries the burden of describing return values and does so only partially via the content-type enumeration. For a paginated, zero-required-parameter, open-world scraping tool it should say that handle or channelId must be supplied and how pagination works, plus distinguish itself from the singular sibling. It is minimum-viable rather than adequate.

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 100%, with each of the four parameters documented inline, including the 'send this or handle' hint and the note that continuationToken is the same as cursor. The description adds no parameter meaning at all, so the baseline 3 for full schema coverage applies.

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 identifies the resource (a channel's community posts) and enumerates what it contains (text, images, polls, likes, comments), which lets an agent infer it is a listing endpoint. However, it is a bare noun phrase with no verb, and it does not differentiate itself from the singular sibling youtube_community_post, so an agent cannot tell from the description alone which one to pick.

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 when-to-use guidance at all: no mention of preferring youtube_community_post for a single post, no indication of when this is preferable to youtube_channel or youtube_channel_videos. The only contextual hint is the content-type list. Critically, nothing states that handle or channelId is required in practice even though the schema marks zero required parameters.

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