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

Beyond the annotations, the description discloses important runtime behavior: the job is enqueued asynchronously, it returns a jobId rather than sending immediately, and it specifies auth modes and likely error codes. This is substantial behavioral context that annotations alone do not provide.

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 compact and front-loaded: the purpose and async behavior come first, followed by targeting rules, auth, errors, and the related tracking tool. Every sentence contributes useful operational information with no filler.

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 tool with no output schema, the description covers the necessary operational surface: what it does, what it returns, when it is not synchronous, how targeting is restricted, which auth modes are valid, likely errors, and how to track the job. This is sufficient for correct selection and invocation.

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 100%, and the schema already documents each parameter and its mutual exclusivity constraints. The description re-emphasizes the exclusive targeting rule and auth-mode behavior but does not add meaningful new semantics beyond what the schema already provides.

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 names a specific action ('Enqueue an asynchronous broadcast job'), the resource ('posting a message to one or more chat rooms of an app'), and the key output ('returns a jobId'). It also clarifies that messages are not sent synchronously, which distinguishes it from related chat-sending tools.

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 gives clear usage context: asynchronous behavior, exclusive targeting modes, auth requirements, and error conditions. It explicitly points to ethora-wait-broadcast-job-v2 as the tracking tool, though it does not name an alternative for synchronous single-room messaging.

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