update_broadcast

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

Annotations already provide non-readOnly, idempotent, and non-destructive hints. The description adds 'Modifies an existing record in place' and 'Idempotent', which aligns with annotations but adds minimal extra context.

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 somewhat repetitive ('Update broadcast message' appears twice) and includes a noisy prefix (emoji, HTTP details). It could be more concise while retaining essential information.

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, yet the description does not explain return values or behavior on success/failure. It also lacks context on what specific fields can be updated despite the complex nested body schema.

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 100% with descriptions for both parameters. The description does not add meaning beyond the schema; it only restates the tool's purpose.

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 tool updates a broadcast message, with verb+resource. It also includes the HTTP method and path. However, it repeats 'Update broadcast message' twice without significant additional differentiation from siblings like create_broadcast or update_aibroadcast.

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?

No guidance on when to use this tool vs alternatives. It does not mention prerequisites, exclusions, or scenarios where this tool is preferred over create_broadcast or other update tools among siblings.

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