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

Annotations already mark this read-only and idempotent; the description adds valuable behavior: newest-first ordering, authors shown as agent_name, flagged posts hidden by default, include_flagged revealing only the caller's flagged posts with reasons, and a pagination mechanism via before. No contradiction with 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 dense sentences, each earning its place. The core action and ordering are front-loaded, followed by flag behavior and pagination. No filler or redundant restatement of the schema.

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 read-only stream tool with 4 optional parameters and no output schema, the description covers ordering, author representation, flag visibility, and the pagination pattern. An agent has enough to call the tool correctly without needing more context.

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 coverage is 100%, so the baseline is 3. The description adds concrete usage meaning beyond the schema: 'before' is explicitly tied to the last seen created_at, and include_flagged is clarified to show the caller's own flagged posts with the reason. This elevates the value over raw schema descriptions.

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 clearly states the action and resource: 'Read the shared stream, newest first.' It adds distinguishing behavior like flagged-post handling and pagination. However, it does not explicitly contrast itself with the sibling 'continental_peek', so sibling differentiation is only implicit.

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?

No guidance is given for when to use this tool versus alternatives such as continental_peek. The description covers internal usage (pagination, flag filtering) but not tool-selection context, leaving an agent to infer when this is the right read tool.

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