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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), it discloses that this broadcasts externally to followers via push and email, that a per-call confirmation applies (with an override option), and that it requires the user's Cotlet API key with app access. This is exactly the kind of behavioral and auth context a mutation/broadcast tool needs.

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 opening is front-loaded, but ideas repeat ('now or at a set time' then 'Send now or schedule with send_at') and the two confirmation sentences ('you can switch that off' vs 'confirm with the user before each call') read as slightly muddled. It's serviceable but not tight.

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 3-param broadcast tool with no output schema, the description covers the important ground: delivery channels, scheduling, confirmation workflow, and API key requirements. Return behavior is unspecified, but that is minor for a send operation whose annotations already carry the safety profile.

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 body, send_at, and artist_id thoroughly. The description echoes send_at scheduling and the Smart Link advice already present in the body schema, adding little new parameter meaning. Baseline 3 is appropriate.

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 and resource ('Sends a Bandsintown post to your followers') and details the delivery channels (push notification and email). It is clearly distinct from event-management siblings like bandsintown_create_event or bandsintown_publish_event, since this reaches the fan audience rather than managing an event.

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?

Gives clear context: send now or schedule with send_at, and it states an explicit confirmation requirement before each call because it reaches other people. It doesn't name or route away from a specific sibling tool, but the when-to-use conditions are well articulated.

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