Set pane talk

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

Since no annotations are provided, the description carries the full burden. It discloses the return value ('resolved talk state and TTS backend'), default state ('off by default'), and warning behavior on backend issues. It does not mention potential permissions or side effects, but the tool is a simple toggle.

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?

Three concise sentences with no fluff: purpose, default, and return behavior. Each sentence earns its place and the key action is front-loaded.

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 simple toggle with two parameters and no output schema, the description is complete. It covers what the tool does, when it applies, its default state, and what it returns, including edge-case warnings.

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 must compensate. It does so by explaining that 'enabled' toggles talk on/off and 'per-pane' implies that paneId targets a specific pane. This adds meaningful context beyond the bare property names.

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?

Description clearly states it 'turn per-pane talk on/off' with a specific verb and resource. It explains the behavior 'speaks NEW Claude assistant replies aloud via local TTS' and differentiates from sibling tools like set_speech by emphasizing 'per-pane'.

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 clear context: it operates on a per-pane basis, affects only NEW replies, and is off by default. It does not explicitly mention alternatives or exclusions, but for a simple toggle this context is sufficient.

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