Open a direct voice inbox window

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

Annotations declare the safety profile (readOnly=false, destructive=false, openWorld=true), and the description adds substantial context beyond them: voice travels directly peer-to-peer with no relay, discovery or recording; invitations/passwords/approvals stay in the visible window; and no sound or pairing secrets are returned to the agent. That is exactly the operational and privacy behavior an agent needs before invoking an open-world session.

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?

Front-loaded and dense with no filler; the operating mode comes first, then behavior, then the return-value caveat. It is slightly packed into one paragraph, but every sentence carries information.

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?

The absence of an output schema is largely compensated by the explicit statement that no sound or pairing secrets are returned. What holds it at 3 is the missing coverage of room_name and ttl_minutes, which leaves an agent unable to set session duration or understand naming constraints from the description.

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 coverage is 0%, so the description carries the full burden, and it only explains the role parameter (host vs sender). room_name and ttl_minutes (default 30, max 120) are never mentioned, leaving an undocumented 80-char name constraint and an expiry the agent cannot reason about from the text alone.

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 (open) and resource (local companion for abox.tools Voice Oncall) and immediately splits it into the two operating modes, host and sender. An agent knows what the tool does, though it never names the close sibling (abox_walkie_session) it must be distinguished from in this crowd of session tools.

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 host listens and moderates incoming senders; a sender grants microphone permission and holds Talk" gives usable role-selection context, which is effectively usage guidance for the required parameter. However, there is no when-to-use versus when-not, and no pointer to alternatives such as abox_walkie_session or abox_camera_session among the many session siblings.

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