set_group_locked

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

Description adds behavioral context beyond annotations: it explains that setting locked=true restricts metadata edits to admins. Annotations already indicate idempotent and non-destructive, but the description clarifies the exact effect on group permissions.

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 succinct sentences that convey the tool's purpose and effect without any unnecessary words. Front-loaded with the action and immediately clear.

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?

Despite good annotations and complete schema, the description does not mention the return value or error conditions. For a simple toggle, this might be acceptable, but missing output info makes it slightly incomplete.

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?

Input schema covers both parameters with descriptions, so baseline is 3. Description adds meaning to the 'locked' parameter by explaining it controls admin-only editing of metadata, which goes beyond the schema's simple boolean description.

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?

Description clearly states 'Toggle locked mode' and explains that when locked is true, only admins can edit group metadata. This specific verb and resource distinction sets it apart from sibling tools like set_group_name or set_group_topic.

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?

Description lacks explicit guidance on when to use this tool versus alternatives (e.g., set_group_announce). It only states the effect without providing usage context or when-not-to-use scenarios.

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