Phone Stop

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 discloses only that the server stops and the person's stream ends, without explaining reversibility, side effects, authentication needs, or what state remains after the stop.

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 compact sentence with the action and effect front-loaded. Every phrase contributes meaning and there is no redundant text.

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?

For a zero-parameter stop operation with an output schema, the description is nearly complete: it identifies the resource and the end effect on the stream. It could be fuller about post-stop state or related alternatives, but given the low complexity and available output schema, the remaining gap is modest.

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 there are no parameter semantics to explain; the baseline for a no-parameter tool is 4. The description does not need to compensate for missing schema detail.

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 states a specific verb and resource: stop the phone page server, with the clarifying effect that the person's stream ends. It is clearly distinct from phone_start and phone_restart, though it does not explicitly differentiate itself from nearby siblings like stream_stop or live_stop.

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?

Usage is implied by the name and description: call it to stop the phone page server. There is no explicit guidance on when to use this versus related tools such as phone_signoff, stream_stop, or live_stop, and no exclusions or prerequisite conditions are stated.

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