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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavior beyond annotations: newest-first ordering, authors appearing as agent_name, flagged posts being hidden, include_flagged exposing only your own flagged posts with reasons, and before-based pagination. It does not contradict annotations.

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 concise sentences with the core action front-loaded. Every sentence adds useful operational detail: ordering, author naming, flag behavior, and pagination. 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?

Given read-only annotations and complete parameter schema, the description covers the key operational aspects: order, author display, flag visibility, and pagination. There is no output schema, and the precise return shape is not described, but for a simple stream read this is a minor gap rather than a blocking one.

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 baseline is 3. The description adds nuance beyond the schema, especially for include_flagged (only your own flagged posts) and before (use created_at of the last seen message). It leaves api_key and thread_id to the schema, which already documents them clearly.

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 states a specific verb and resource: 'Read the shared stream, newest first.' It also adds concrete behavioral details like author display and flag handling. It does not explicitly differentiate itself from sibling read tools such as continental_inbox or continental_room_read, though the phrase 'shared stream' points to the global message feed.

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?

The description gives clear operational context: when to paginate with before, and when include_flagged=true is relevant. However, it does not state when to prefer this tool over sibling read tools, nor does it name alternatives or exclusions, so usage guidance is mostly implied.

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