create_recipient_group

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

Annotations already signal non-read-only and non-idempotent behavior, so the description's added value is the explicit authorization requirement, 'requires write permission'. This is a useful behavioral trait beyond the structured annotations, though the description does not cover potential duplicate-name failures or response 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?

A single front-loaded sentence contains the action and a key prerequisite without filler. Every word contributes meaning, and the tool's scope is 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?

For a simple, three-parameter create operation with complete schema coverage and safety annotations, the description plus schema provide enough to call the tool correctly. It does not describe return values, and no output schema exists, but none are essential for invocation.

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%, so each parameter is already documented in the input schema. The description itself adds no parameter-level meaning beyond the operation, matching the baseline for full schema coverage.

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 the imperative 'Create' with a specific resource, 'recipient group', and is clearly distinguished from sibling update/delete/get tools by the create verb. It states the operation concisely and unambiguously.

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 conveys the basic context for using the tool (creating a new recipient group) and adds a permission prerequisite, 'requires write permission', but it never explicitly contrasts with alternatives such as update_recipient_group or delete_recipient_group. Usage guidance is therefore implied rather than explicit.

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