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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior, so the safety profile is covered. However, the description adds nothing beyond that—no ordering, size limits, pagination, or whether the list is scoped to the authenticated promoter. For a zero-argument list tool, this leaves the agent with no behavioral context at all.

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?

It is a single short fragment with no wasted words and the scoping detail is front-loaded, but the brevity reflects under-specification rather than discipline—there is only one idea present and it barely exceeds the tool name.

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?

An output schema exists, so return values need not be described, and there are no parameters to explain. What is still missing is sibling differentiation (why not search_artists) and any hint about scope or emptiness, which matters given how crowded the sibling set is.

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 schema has zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool is 4. No parameter information is missing or contradicted.

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 phrase 'Artists the promoter is watching' conveys the resource being returned, but it is essentially a restatement of the tool name 'Watchlist' rather than a specific verb+resource statement. It does add the scoping detail that entries are per-promoter within Callboard, which helps slightly, but it does not distinguish this from siblings like search_artists or fetch.

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?

There is no guidance on when to call this versus search_artists or fetch, no mention of prerequisites, and no indication of what an agent should do if the watchlist is empty. Usage must be inferred entirely from the tool name.

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