Set streaming status to ended

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds a concrete operational constraint, the 100 requests / 10 seconds per shop rate limit, which is genuine value beyond annotations. It does not explain what 'ended' implies for the stream or why the confirm flag exists.

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?

Two short elements with zero waste; the rate-limit constraint is front-loaded and the purpose sentence follows. Nothing redundant or padded.

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 5 parameters, zero required fields, a nested payload object, and three apparently exclusive ways to supply the body (payload, payload_file, services), the description never clarifies which to use or what confirm is for. Annotations cover the destructive profile, but the invocation-shape ambiguity is left entirely to the schema.

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?

Schema description coverage is 80%, so the schema does most of the work and 3 is the baseline. The description's phrase 'for specified services' loosely maps to the services parameter, but adds nothing about the mutually exclusive payload / payload_file / services body mechanisms or the confirm flag.

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?

States a specific verb and resource: 'Sets streaming status to ended for specified services'. Combined with the name end_streaming, an agent can tell it apart from the sibling start_streaming and get_streaming_status without opening schemas. It does not explicitly name those siblings, so it falls short of a 5.

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?

No when-to-use guidance, no stated prerequisites (e.g. an active stream, a prior start_streaming call), and no alternatives or exclusions. The only usage-adjacent content is a rate-limit note, which is a constraint rather than selection guidance.

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