broadcast_spatial_notification

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions connecting to the Spatial Voice Agent but does not describe any side effects, permission requirements, or state dependencies (e.g., whether the viewer must be active). This lack of detail hinders safe invocation.

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 extremely concise: two sentences that front-load the action and quickly explain the mechanism. Every word contributes value, making it easy for an agent to parse.

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?

Given that an output schema exists and the input schema covers all parameters, the description is minimally adequate. However, it lacks any mention of prerequisites (e.g., active viewer) or behavior when conditions are not met, leaving potential gaps for an agent relying solely on this 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?

All parameters are already well-documented in the input schema (100% coverage). The description adds little beyond 'spatial' and '3D world' context, which is already implied by the schema's coordinate parameters. Thus, baseline 3 is appropriate.

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 clearly states the tool's purpose: broadcasting a spatial voice notification to the active World Labs Spark Viewer, narrating specific locations. It uses specific verbs and resource, and implies differentiation from sibling 'broadcast_spatial_audio' by focusing on voice notification and text-to-speech via Gemini TTS.

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 provides no explicit guidance on when to use this tool versus alternatives like 'broadcast_spatial_audio'. It implies usage for narrating locations but does not specify when not to use it or mention any prerequisites such as having an active viewer.

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