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

Goes well beyond idempotentHint/destructiveHint by disclosing real consequences: 'off' still measures but never posts, 'preview' records without sending, nudges never DM under 'public', and human-approval in Slack is required regardless of posture. It also clarifies there are no per-capability settings, which prevents an agent from assuming granular override 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?

Front-loaded with the core purpose before the enum walkthrough, and every sentence carries decision-relevant information. It is somewhat long because the enum meanings appear in both the description and the schema, which is mild redundancy rather than waste.

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 single-parameter mutation tool with an output schema available, the description covers the safety profile, the permission requirement, the approval fallback, and the read sibling. There is nothing an agent needs in order to call it correctly that is missing.

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% and the enum values are already documented in the schema, so the baseline is 3. The description earns extra credit by adding semantics the schema lacks — notably that 'off' still measures and 'preview' records recommendations without sending — but it largely restates the enum list rather than adding format or edge-case behavior.

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?

Names a specific verb and resource ('Set how loudly the Coderbuds agent speaks to this team') and immediately frames it as 'the single control over whether it acts at all,' which delineates it from every read-only sibling. An agent can distinguish it from get-agent-activity-tool or the many get-* tools without opening a 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?

It enumerates every posture value with its operational meaning, states the prerequisite (team admin permissions), and explicitly routes to get-agent-activity-tool to inspect current posture and activity. The only mild gap is the absence of an explicit 'when not to use' clause, but the read-vs-write split with the named sibling covers the practical alternative.

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