set_project_slack

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds that this is an admin action and that it involves a bot-token secret reference, but it does not disclose that existing Slack settings may be overwritten, how the secret reference is handled, or what confirmation is returned.

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 description is a single front-loaded sentence with no wasted words, and the administrative framing is placed first. It is efficient, though its brevity contributes to the missing usage and parameter details.

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?

This is a destructive, idempotent mutation involving sensitive bot-token references, with five parameters at 0% schema coverage and no output schema. A single sentence cannot adequately cover the undocumented 'as_agent' parameter, overwrite behavior, secret handling, or expected outcome, leaving significant gaps for an agent to call it correctly and safely.

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 0%, so the description must carry the burden. It indirectly names the workspace, default channel, and bot-token secret fields, but it never mentions the 'as_agent' parameter or clarifies which fields are required versus optional, nor does it explain formats for IDs or secret references.

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?

The description uses a specific verb ('configure') and resource ('Slack workspace, default channel, and bot-token secret reference for a project'), and names the exact settings it modifies. It is clearly distinguishable from all sibling tools, none of which touch Slack configuration, though it does not explicitly state what it is not.

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 'Admin:' prefix implies this is an administrative operation, giving some usage context, but there is no explicit guidance on when to use this versus any alternative, no stated prerequisites, and no exclusions. Usage is implied rather than explained.

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