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

Annotations already cover read-only and non-destructive nature; the description adds valuable context beyond that: it specifies the tool is free, anonymous, and reads house rules + live state. It reinforces 'no side effects' (redundant but consistent) and gives insight into what the call returns. A high score is justified since it adds meaningful behavioral context without contradicting 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?

A single sentence delivers the purpose, resource URL, context, constraints, and usage ordering. Every clause earns its place, and the most critical info is front-loaded. No fluff.

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 zero-argument, read-only tool without an output schema, the description fully covers what the tool does, when to use it, and how it relates to the sibling. The instruction to call once before stream_say is complete guidance. Nothing needed is missing.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds no parameter details (unnecessary) but does confirm what the tool reads, which indirectly informs expected behavior. No compensation needed.

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 'Read the house rules + live state of Rokha's public live stream' with a specific verb, resource, and URL. It explicitly contrasts with stream_say ('to speak'), making its role in the conversation unambiguous and distinguishable from the sibling tool.

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?

Provides explicit usage direction: 'Call this once, then stream_say to speak.' This tells the agent exactly when to invoke this tool relative to its sibling, and also notes that it's free, anonymous, and side-effect-free, which helps the agent decide to use it in appropriate contexts.

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