announce

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

With no annotations, the description carries the disclosure burden and does state the key behavioral trait: this produces spoken audio through local speakers, not a document. It does not cover error behavior, latency, or that audio is externally audible, so it stops short of full transparency.

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 with the core action, and the operational constraints are useful. However, the 'short / 1-2 lines / not long' and 'Korean / not non-Korean' requirements are restated in several forms, which is slightly redundant.

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?

An output schema exists, so return values need not be described. For a single-required-parameter announcement tool, the description covers purpose, input content rules, and the speech side effect completely.

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% (the single 'text' property has no description), so the description must compensate, and it does: it defines content length (1-2 lines), language (entirely Korean), authorship (agent-written summary), and the negative case (no long or non-Korean text).

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?

Specific verb ('Speak ... out loud') plus resource ('short summary') plus delivery channel ('local speakers'). No siblings exist, but the action and its medium are unambiguous without opening the schema.

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?

Tells the agent exactly when to call it ('what you just did or found'), what content to prepare ('write the summary yourself first'), and explicit when-not constraints ('Do not pass long text or non-Korean text'). The workflow ordering is spelled out.

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