advertise_ready_streams

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

No annotations are provided, so the description carries the full behavioral burden. It implies a bulk mutating operation against TAK Video Manager but says nothing about idempotency (are already-advertised paths re-POSTed?), auth/permission requirements, partial-failure behavior, or side effects on the TAK side.

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 front-loaded sentence with no filler — the action, scope, and destination are all in the first clause. Nothing to trim.

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?

An output schema exists, so return values need not be described. However, for a no-arg bulk write operation with no annotations, the description omits failure modes, idempotency, and prerequisites, leaving the agent unable to predict what happens on a second invocation.

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 takes zero parameters, so the baseline of 4 applies; there is no parameter semantics for the description to clarify.

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?

Names a specific verb (POST), a specific resource subset (every ready MediaMTX path), and the destination system (TAK Video Manager). It is distinguishable from mediamtx_paths, which merely lists paths, though the description never names that sibling to make the contrast explicit.

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 invoke this versus mediamtx_paths or tak_publish_video, no stated prerequisites (e.g. that paths must be in a 'ready' state, or that MediaMTX must be reachable), and no indication of when not to run it.

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