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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutation/idempotency profile is covered. The description adds value beyond structured data by disclosing the hidden side effect: a signature is generated per teammate from the group's template. It does not say what happens to an existing signature or whether template absence causes failure, keeping it below a 5.

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 short sentences, both informative, with the primary action stated first and the consequence second. No filler or redundant restatement of the title.

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 two-parameter tool with annotations covering safety and no output schema, the description covers purpose, side effect and usage cue. The main remaining gap is precondition/error behavior (missing template, already-assigned teammate), which is minor given the annotation set.

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% and both parameters already point to list_groups and list_teammates as the source of ids. The description adds no further meaning about group_id or teammate_ids, so 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?

States a specific verb (assign) and resource (teammates to a group) and adds the resulting side effect: each teammate gets a signature built from the group's template. This makes it unmistakable versus the inverse sibling remove_teammates_from_group and versus update_teammate.

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?

"This is how a person gets a signature" gives an explicit context for reaching for this tool rather than get_teammate_signature or preview_signature. It stops short of stating preconditions (group must have a template) or naming the alternative explicitly, so it is clear context without exclusions.

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