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

Annotations are thin (only readOnlyHint=false), so the description carries most of the burden. It does disclose that this is a privileged mutation requiring moderator+ and constrained to voice-capable channels, which is real added context. It is silent on what happens when the capability check fails, whether the operation is idempotent, and what a revoke does to an active floor holder.

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?

Two sentences, no filler, with the action and its scope front-loaded before the precondition. Every clause carries information the agent needs.

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 simple 3-required-parameter boolean toggle with a fully documented schema and no output schema, the description covers action, target, capability gate and permission requirement. The only real gap is failure/idempotency behavior, which is a modest omission rather than a blocker.

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 100%, so all three parameters are already documented, including the meaning of ptt_enabled and where to source the UUIDs. The description adds only the target framing ('for a member'), not format or edge-case semantics. 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?

Specific verb pair ('grant or revoke') plus a precise resource ('PTT floor permission') and scope ('for a member in voice-capable channels'). An agent can distinguish this from mTALK_press/release (which operate the floor, not the permission) and from mIRC_set_role. It stops short of naming a sibling explicitly, so not a 5.

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?

Supplies two concrete gates: the channel must have capabilities.ptt=true and the caller must be moderator+. That is clear invocation context. It does not state exclusions or what to do instead when the channel is not voice-capable, so it falls below the explicit when/when-not bar of a 5.

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