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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the safety profile is covered. The description adds real delivery semantics beyond that: opt-in gating, the @CrewPay_Bot channel, and the negative scoping note 'Never uses channel member counts.' It does not mention rate limits or delivery failure behavior.

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?

Two tight sentences with the action front-loaded and the constraints following immediately. Every clause earns its place, and the non-obvious negative constraint is included without padding.

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 three-parameter, all-optional notification tool with no output schema, the description covers what the agent must know: who gets messaged, through which bot, and the opt-in requirement. Only the success/failure semantics of a send remain unstated, which is a minor gap.

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 explains mint, handles, and message, including the 'if mint is omitted' fallback. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema carries the burden.

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: 'DM hired KOLs via @CrewPay_Bot.' An agent can tell this is an outbound notification to already-hired crew rather than a discovery or listing tool like crew_list_kols. It stops short of naming a sibling tool it should be preferred over, so it does not reach a 5.

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 gives a concrete precondition ('Opt-in only: they must have linked Telegram, sent /start, and enabled alerts'), which tells the agent when the call will actually deliver. It never contrasts this tool against alternatives such as crew_list_kols or crew_autohire, so the when-not guidance is implicit rather than explicit.

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