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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=false), yet the description adds real context: requires authentication and read permission, custom-target restrictions apply, and pages are capped with a continuation token. It does not mention rate limits or failure modes, so a 4 rather than 5.

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?

Four tight sentences, purpose front-loaded, followed by permission requirements, return/pagination shape, and sibling routing. No filler or repetition of the title.

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 an output schema present, the description does not need to explain return values, and it still supplies the operational essentials an agent needs: auth/permission requirement, page size limit, continuation token semantics, ordering, and when to pick an alternative tool.

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%, so the schema already documents id, limit, toDate, fromDate, and nextToken with formats and bounds. The description only frames the parameters' purpose ('date bounds for historical updates', 'optional continuation token') without adding syntax or constraint detail, so the baseline 3 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?

States a specific verb+resource ('Read one page of stored posts from an accessible Synoptic stream, newest first'), including scope and ordering. It distinguishes itself from siblings by explicitly naming search_stream_posts and by negating monitoring/external-fetch behavior.

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 concrete routing conditions: use date bounds for historical updates, use search_stream_posts for text queries. It also states the boundary condition that this call reads existing content only and does not start monitoring or fetch external sources.

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