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

Annotations already declare readOnly/non-destructive/openWorld, so the description's added value is the pagination model ('one page'), the absence of a feed-enumeration capability, and that name matching is partial — all behaviors not in the annotations. It does not say what a page contains or how to detect more pages.

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?

Three terse clauses front-load the scope, then the precondition, then the endpoint. No filler; every phrase contributes information an agent cannot get from the schema or annotations.

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 simple read-only paginated list with a small flat schema, the description establishes the retrieval scope, the pagination unit, the prerequisite ID source, and the filter semantics. Return values are not needed since no output schema exists but 'posts' is unambiguous here.

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?

With 0% schema description coverage the description must compensate: it clarifies that name is a partial match and that feed_id must come from Givecloud externally. But page and especially include (enum: categories, postType) receive no explanation at all, leaving half the parameters opaque.

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 with scope: 'Read one page of posts in a known feed.' The paginated-list framing clearly separates it from the single-item sibling givecloud_get_post, though it never names that sibling explicitly.

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?

'Obtain the feed ID in Givecloud; this connector does not enumerate feeds' is a genuine precondition plus an explicit exclusion, telling the agent when this tool is unusable. It stops short of routing to a sibling for single-post retrieval or feed discovery.

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