sigma_deactivate_member

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

Annotations already indicate readOnlyHint=false and destructiveHint=true. The description adds the critical behavior that the operation requires confirm=True, which is not in annotations and provides important safety context. However, it does not disclose other behavioral traits like reversibility or side effects.

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 two short sentences, with no fluff. It front-loads the core action and immediately highlights a crucial parameter requirement. Every word earns its place.

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?

Given the presence of annotations, an output schema, and a simple action, the description covers the essential operational requirement (confirm=True). It lacks deeper context such as what 'deactivate' means practically or any preconditions, but for a straightforward destructive action with annotations, it is reasonably complete.

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 0%, so the description must compensate. It explicitly explains the confirm parameter's purpose (required for deactivation) but provides no information about member_id beyond what the schema already shows. This partial compensation warrants a middle score.

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 'Deactivate a member' uses a specific verb and resource, clearly indicating the action. It is distinct from sibling tools like sigma_delete_team and sigma_update_member, and the mention of 'confirm=True' adds a key operational detail.

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 description states 'Requires confirm=True', which is a necessary precondition but lacks explicit comparison to alternatives or guidance on when to use this over other member management tools. The context is somewhat implied but not fully articulated.

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