Stream a board-level chat response (requires enableConferenceRoomChat)

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

The description says 'stream' which implies a streaming response, but no details about streaming behavior (e.g., how to handle chunks, termination). Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds minimal behavioral context beyond the streaming aspect.

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 short (two sentences) and front-loaded with the title and requirement, but the lack of parameter documentation and streaming details makes it less valuable than it could be. It is concise but incomplete.

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 the tool has a complex streaming behavior, nested parameters, and an output schema, the description lacks critical context: no explanation of the streaming format, error handling, or parameter roles. It only covers the prerequisite and auth class.

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 one parameter 'body' with nested required fields, but schema description coverage is 0%. The description does not explain the meaning or purpose of any parameter (e.g., companyId, message, taskId), forcing the agent to infer from names 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?

The title and description clearly state the tool streams a board-level chat response, with a specific prerequisite. It stands out from the many sibling tools due to its specific domain.

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 specifies the requirement 'requires enableConferenceRoomChat' which is a clear usage guideline. However, it does not explicitly indicate when to use this tool versus alternatives or when not to use it.

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