List LIVE watermarks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and world access are covered. The description's '[READ]' tag merely repeats the read-only annotation and adds no further context about authentication, pagination, rate limits, or what data is returned. It does not contradict the annotations, but it contributes very little behavioral detail.

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 short line, so it is not verbose. However, its brevity reflects under-specification rather than efficient communication of useful information; the '[READ]' tag is redundant with annotations and the OpenAPI path adds little for an agent.

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?

With no output schema and no parameter schema, the description is the main source of context, yet it does not explain what 'live watermarks' are or what listing them returns. For a discovery-style tool, the agent is left with a cryptic resource name and no indication of the response shape or use case.

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 tool has zero parameters, so the schema cannot document any and baseline is 4. The description correctly does not invent parameter details where none exist.

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 essentially restates the tool name and HTTP endpoint: '[READ] OpenAPI: GET /watermarks'. It does not explain what a watermark is in this API, what the LIVE scope means, or how it differs from sibling tools like list_live_streams or get_live_domain. An agent learns almost nothing beyond the name itself.

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?

There is no guidance on when to use this tool, when not to, or which alternatives exist. The description provides only the HTTP verb and path, leaving the agent to infer usage from the name alone.

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