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

Annotations already declare readOnlyHint=true, so 'Read-only observability' largely restates structured data, though it does confirm the intent of the call. The genuinely additive detail is the cursor-pagination disclosure and the underlying API mapping (GET /broadcasts), but return shape and page-size defaults are left unstated.

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?

Three short sentences/fragments with no filler, and the pagination behavior is front-loaded right after the action. 'Project API: GET /broadcasts' is dense but useful for agents that reason about API surfaces; nothing is redundant.

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 zero-required-parameter list endpoint with a fully documented schema and no output schema, the description covers the essential facts: what a broadcast is, that results are paginated, and that the call is read-only. Only the return item shape and default page size are absent, which is acceptable given the simple 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 description coverage is 100%, so limit, ending_before, and starting_after are fully documented in the schema. The description's mention of 'cursor pagination' is consistent with that but adds no syntax, defaults, or ordering semantics beyond it, so the baseline 3 applies.

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?

States a specific verb+resource ('List broadcasts') and helpfully defines the domain term as 'notification-send batches', which removes ambiguity for an agent unfamiliar with MagicBell's vocabulary. It does not explicitly name the sibling get_broadcast as the single-item alternative, so it stops just short of full sibling differentiation.

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?

'Read-only observability' implies the context (inspecting sent batches) but there is no explicit when-to-use/when-not or pointer to an alternative such as magicbell_get_broadcast for a single item. Usage is inferable from the name and the observability framing rather than stated.

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