List Stream Radar flags

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

The description adds significant behavioral context beyond the readOnlyHint annotation: it explains the paginated nature, available filters, and the critical limitation that the feature is optional and returns 403 if not enabled. No contradictions.

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 two sentences long, front-loaded with the main action, and includes essential additional context about the add-on requirement. No unnecessary words or repetition.

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 output schema, the description does not describe the response structure, which would be helpful. However, it does convey the purpose, filtering, pagination, and a critical limitation (403 if not enabled). For a list tool with many filters, this is fairly complete but could hint at output fields.

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 description lists the filterable fields (status, severity, dsp, isrc, release_id, detected_from/detected_to), which adds context for parameters that lack schema descriptions (isrc, page, per_page, release_id have no descriptions in schema). However, it does not provide detailed semantics for each parameter beyond what the schema already describes.

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 lists 'Stream Radar flags' and explains they are early-warning flags for possible artificial-streaming activity. It distinguishes from sibling 'get_stream_radar_flag' by being a paginated list operation.

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 mentions filtering options and explicitly warns that Stream Radar is an optional add-on, without which the API returns a 403. It does not, however, compare to alternative tools like 'list_artificial_streams' or describe when not to use this tool.

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