Get stream state

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

Annotations already declare readOnlyHint and openWorldHint. The description adds valuable context: platforms with no data are omitted, and clarifies that 'live' is the closest indicator for Lumia stream mode. This goes beyond the annotations without contradicting them.

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 concise, with two sentences and a note. It front-loads the main purpose and key data fields, then adds important details about omissions and caveats. No extraneous words.

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 the tool has no parameters, no output schema, but comprehensive annotations, the description fully explains what the tool returns. It covers data fields, per-platform breakdown, totals, omission handling, and a nuance about live status. It is complete for the tool's complexity.

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?

The input schema has no parameters and schema description coverage is 100%. Since there are no parameters, the description does not need to explain them. It correctly focuses on describing the output.

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 gets a snapshot of the current stream and enumerates specific data fields (streamer name, live status, now-playing song, heart rate, per-platform breakdown, cross-platform totals). The verb 'get' and resource 'state' are specific, and it distinguishes from siblings like set_stream_info or get_variable by its comprehensive read-only nature.

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 does not explicitly state when to use this tool over siblings, but it implies usage for obtaining a full state snapshot. There is no mention of alternatives or exclusions, so the agent must infer from context.

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