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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation, so safety is covered. The description adds genuinely new context the annotations cannot convey: the required incoming webhook from a Slack app with Incoming Webhooks enabled, and the Starter-plan gating. It stops short of describing failure modes or post-add behavior, so not a 5.

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 tight sentences: the action first, then the setup prerequisite, then the plan requirement and sibling routing. No filler, and the most decision-relevant information (what it does, what it needs, what to use instead) is front-loaded.

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?

With five parameters at full schema coverage, annotations covering the mutation profile, and no output schema, the description supplies the missing operational context (webhook source, plan tier, alternatives). Only a minor gap remains around what happens after the destination is added (e.g., verification or immediate effect).

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 coverage is 100%, so form_id, webhook_url, color, username, and avatar_url are all documented in the schema itself. The description only reinforces the webhook URL format/prefix, which is marginal value over the schema. 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 and resource ('Posts each submission to a Slack channel') and immediately names the sibling alternatives (bootform_add_discord, bootform_add_webhook) for adjacent use cases. An agent can distinguish this from the other destination tools without reading any schema.

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 an explicit when-to-use condition ('when the person wants submissions in Slack') and explicit routing rules to the Discord and generic webhook siblings. It also names the exact prerequisite artifact and plan tier, leaving nothing to inference.

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