post_stream_digest

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

No annotations are provided, so the description carries the burden. It implies a read-only analysis by listing output types (totals, trend, top videos). It does not mention authorization, rate limits, or side effects, but the behavioral implication is clear.

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?

The description is a single sentence that efficiently conveys purpose, parameters, output content, and usage hint. Every part earns its place, and the key information is front-loaded.

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?

Despite lacking an output schema and having 0% parameter schema coverage, the description covers the key outputs (totals, per-day trend, top videos) and the input format. It could elaborate on what 'totals' and 'trend' entail, but for a digest tool, it is sufficiently complete.

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 0%, so the description must compensate. It mentions 'date window (YYYY-MM-DD)' and hints that 'end' might be yesterday ('run it the morning after'), adding context. However, it does not specify inclusivity or exclusivity of dates.

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 tool provides a channel performance digest for a date window, listing totals, per-day trend, and top videos. It distinguishes from siblings like 'channel_report' and 'top_videos' by focusing on a digest with specific content and timing.

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 explicitly suggests 'run it the morning after a stream', providing a clear usage context. However, it does not explicitly state when not to use it or compare with alternatives.

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