Get Broadcast Job

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds substantial context beyond annotations: the one-shot no-polling nature, the requirement that auth must match the enqueue auth, the prerequisite of having a room, and specific error codes (401/403/404). These details go well beyond what the annotations convey, though they don't specify what happens to results after fetching.

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 densely informative: purpose, mode, prerequisite, auth, errors, and related tool are covered in a few sentences. The most critical detail (one-shot, no polling) is front-loaded, and every sentence earns its place.

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 simple status-fetch tool with no output schema, the description covers all essential aspects: purpose, behavior, prerequisites, auth modes, error codes, and the sibling for blocking waits. No critical gaps remain for an agent to call this tool correctly.

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%, so the schema already documents both parameters thoroughly. The description adds meaning by explaining `jobId` is returned by `ethora-chats-broadcast-v2` and clarifying when `appId` is required versus ignored. This is a modest but real value-add over the schema.

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 states a specific verb ('Fetch') and resource ('current status and per-room results of a broadcast job by jobId'), and it explicitly distinguishes itself from the sibling `ethora-wait-broadcast-job-v2` by noting it is one-shot with no polling. This makes the tool's purpose precise and clearly differentiated.

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 explicitly provides when-to-use context ('one-shot, no polling'), contrasts with the blocking alternative `ethora-wait-broadcast-job-v2`, and gives prerequisites, auth mode requirements, and error codes. An agent can reliably decide when to call this tool versus the sibling.

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