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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely useful behavior: access rechecking, empty-page-with-cursor semantics, and the 50-post page cap. It stops short of describing the returned post shape, though an output schema exists.

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 sentences, no filler, and the scope constraint (owner, 50-post cap) is front-loaded. The paging caveat is a legitimately necessary second half.

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 paginated, nested-filter read tool with a full schema and an output schema, the description covers the tricky parts an agent would otherwise get wrong: cursor continuation on empty pages and rechecked access. Return values are appropriately left to the output schema.

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%, including detailed nested matchFilter fields, so the baseline is 3. The description only summarizes the filter concept ('matched crypto or prediction markets') without adding syntax or semantics beyond what the schema already states.

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 ('Read up to 50 stored posts from a collection'), and adds scope ('owned by the signed-in user') plus optional market matching. It distinguishes itself implicitly from get_stream_posts and search_stream_posts by naming collections, but never names a 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?

Gives operational guidance for paging (continue with nextToken when a page is empty) and notes access is rechecked, but never says when to choose this over get_stream_posts or search_stream_posts, so the sibling choice is left to inference.

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