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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive mutation. The description adds real value beyond them by disclosing that the message is spoken into the shared voice conversation and that session spending and duration limits continue to apply — billing-relevant context an agent would not otherwise know.

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?

Two sentences, both load-bearing, with the core action and its voice-sharing effect stated first and the cost/limit caveat second. No redundancy or filler.

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?

No output schema exists, and the description does not say what the call returns, whether the avatar responds synchronously, or what happens when the session is inactive. For a 3-parameter mutation with zero schema coverage, the behavioral picture is only partially filled in.

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 description coverage is 0%, so all three parameters (workspaceId, avatarSessionId, message) are undocumented in structured data. The description clarifies the message parameter ('typed question', 1-4000 chars implied by schema) but adds nothing about how workspaceId and avatarSessionId are obtained or their format.

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 (send) and resource (a typed question into an active avatar session) with the notable scope qualifier 'sharing its voice conversation'. An agent can distinguish it from start_live_avatar_session / stop_live_avatar_session / get_live_avatar without opening schemas, though no sibling is named explicitly.

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?

'Into an active avatar session' implies the session must already be running, which implicitly points at start_live_avatar_session as the prerequisite, but the description never states when to use this versus other avatar tools or what to do if the session is not active.

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