modify_broadcast

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

With no annotations, the description carries full burden. It mentions 'pending batches' and 'active broadcast', implying it does not affect already sent messages. However, it does not disclose what happens to batches in flight or required preconditions.

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?

Single, efficient sentence with no redundant words. Front-loads the action and resource clearly.

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, no annotations, and only 3 parameters. Description omits return values, error conditions, and prerequisites like whether the broadcast must be active. Incomplete for a tool that modifies a running broadcast mid-run.

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 33% (only 'body' has a description). The description does not add semantics for 'botid' or 'broadcastId', and the existing schema description for 'body' is minimal. Description fails to compensate for low schema coverage.

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 clearly states the verb 'Modify', the resource 'message body for pending batches of an active broadcast', and the context 'mid-run'. It distinguishes from sibling tools like 'delete_broadcast' and 'stop_broadcast' by specifying what is modified.

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?

Implies usage context (mid-run, pending batches, active broadcast) but does not explicitly state when to use vs. alternatives like 'stop_broadcast' or 'delete_broadcast'. No when-not-to-use guidance.

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