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

Annotations declare destructiveHint=true and non-idempotent, so the safety profile is partly covered. The description still adds real behavioral consequence the annotations cannot express: auto approval skips human review and can publish as soon as a post is submitted. It stops short of stating what a channel update overwrites or whether settings changes are reversible.

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?

Front-loads the core action and the sibling exclusion in the first two clauses, then conveys the approval caveat. The em-dash-heavy phrasing and the trailing "Related:" list add some weight without much payoff.

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?

Output schema exists, so return values need no explanation, and the riskiest parameter plus the primary routing decision are both covered. The trailing sibling list is thin padding, and the description never notes that this is a destructive mutation (e.g. active=false retires a channel), which the agent would have to infer from annotations and 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 coverage is 100%, so the baseline is 3. The description goes beyond the schema for the highest-risk parameter by explaining the downstream effect of approval=auto versus required, which the enum description only states tersely. Other parameters (active, icpFit, notes, bioDestination) get no added meaning, keeping it below 5.

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 ("Updates a channel's settings") and immediately scopes it by naming the sibling it is not — posting frequency belongs to update_posting_slots. An agent can route correctly without opening the 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?

Names the alternative tool (update_posting_slots) for the adjacent concern, and gives an explicit when/when-not rule for approval=auto: only when the workspace has chosen to skip review for that channel. That is genuine decision guidance, not implied usage.

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