mailkite_get_broadcast

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

Annotations already indicate readOnlyHint=true, and the description complements this with the additional requirement of a management session token and a preview of the response contents. It does not cover errors or response format details, but for a simple read operation this is a reasonable level of disclosure.

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 two short sentences with no wasted words. It front-loads the action and result, then adds the auth requirement, making it highly scannable for an agent.

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 one-parameter read-only tool, the description covers the key aspects: what is fetched, what the response highlights, and the required token. Since there is no output schema, a bit more detail about the returned recipient summary fields could help, but nothing critical is missing for invoking the tool.

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?

The only parameter, id, already has 100% schema coverage, so the description is not obligated to document it heavily. It adds the context that the id refers to a broadcast, but provides no extra format, source, or validation detail beyond what the tool name and schema already imply.

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 action ('Get'), the resource ('one broadcast'), and the distinguishing output ('status and recipient summary'). It is unambiguous and easily differentiated from broadcast-list, create, update, delete, and send siblings.

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 singular 'one broadcast' implies this tool is for individual retrieval rather than listing all broadcasts, and the token requirement sets an operational prerequisite. It does not explicitly name alternatives like list_broadcasts or state when not to use it, but the context is clear enough.

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