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

With no annotations, the description must carry the behavioral disclosure burden. It adds useful context beyond the schema: results are scoped to the authenticated user and include live video and session state. However, it does not mention pagination, empty-result behavior, or any limits or caveats around the 'live' data.

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 compact sentence front-loads the action, resource, scope, and returned content. Every word earns its place, with no redundancy or restatement of the tool title.

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 tool with no annotations and no output schema, the description gives a reasonable high-level picture of the result but leaves the exact return shape and edge cases unspecified. It is adequate for basic invocation, yet an agent would need more detail to confidently parse the response.

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 input schema has zero parameters and 100% schema description coverage, so there is nothing for the tool description to add. The baseline for a zero-parameter tool applies, and no parameter detail is missing.

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 ('List'), a clear resource ('farm phone slots'), a scope ('the authenticated user can view'), and the included data ('live video and session state'). It also distinguishes itself from sibling tools like list-phone-runs-tool by targeting current slots rather than run history.

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 implies use when an agent needs the phone slots visible to the current user, but it does not explicitly contrast with sibling tools or state when not to use it. No alternative routing is provided, so usage guidance remains implicit rather than explicit.

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