send_announcement

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

With no annotations, the description carries the burden of disclosing behavioral traits. It reveals a critical requirement (confirm='SEND'), which is a safety mechanism. However, it does not describe side effects, whether the action is irreversible, or what the response contains. The reference to 'preview' adds some context but lacks detail.

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 short sentences that front-load the core action and immediately note the critical requirement. No unnecessary words, though the phrase 'which the preview explains' is slightly vague and could be more specific.

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?

The description covers the essential action and the confirmation parameter, but for a tool with no output schema and no annotations, it leaves gaps: the effect on recipients, any prerequisites besides confirm, and the relationship to the preview tool are not fully explained. It is minimally viable but not comprehensive.

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%, and the description only mentions the `confirm` parameter (and only its allowed value). The meanings of `course`, `title`, and `message` are left entirely to the schema names. This is insufficient compensation for the lack of schema documentation.

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 'Post an announcement' provides a clear verb and resource, indicating a send/publish action. It does not explicitly differentiate from sibling tools like 'create-announcement' or 'preview_announcement', but the term 'send' implies final delivery, which is distinct enough.

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 mention that `confirm='SEND'` is required and that 'the preview explains' gives clear contextual guidance on prerequisites and the intended workflow (likely preview before send). It does not explicitly name the preview tool or list exclusions, but the context is sufficient for basic usage.

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