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

Goes well beyond the annotations (which only say non-readonly/non-destructive/non-open-world): it discloses the default (50), the 0 = never convention, the backfill side effect of raising the threshold with its recent-history exception, the 'selected chats' and 'new messages only' account behaviors, and the required owner/admin permission. It does not describe the return shape for a setting with no output schema, and the state-setting semantics sit slightly uneasily with idempotentHint=false.

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 leading sentence front-loads the action before any detail, and the following sentences are information-dense rather than filler. It is a long paragraph with a decorative emoji and some nested parentheticals, which costs a point on tightness.

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 mutation tool with no output schema, the description covers semantics, side effects, and authorization thoroughly. The remaining gaps are the return confirmation and whether effects are limited to the referenced account — minor but non-zero.

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, but the description adds real meaning for large_group_threshold: the default, the 0 sentinel, where to read the current value, and what changing it downstream does. The in_workspace parameter is left entirely to the schema, so it is not a full 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 ('Change how large a group can be and still sync on one connected account') rather than restating the tool name. It also distinguishes itself from the sibling threads.update, noting that a single chat can be switched on there instead. An agent can tell what this tool tunes 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?

Gives concrete usage context: the current value lives in channels.list(account_id=...), the default is 50, and raising vs. lowering has different effects. It also names the alternative (threads.update(synced=true)) for switching on a single chat. No explicit 'do not use when...' case, so 4 rather than 5.

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