AccessGroupsAddMembers

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

Annotations already establish that the tool mutates state (readOnlyHint=false) and is not idempotent. The description adds no extra behavioral context such as duplicate handling, whether existing memberships are replaced, or authorization requirements.

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 a single concise sentence with no wasted words, and the core action is front-loaded. It is efficient, though it is so terse that it mostly restates the tool name and could be slightly more informative without harming conciseness.

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 mutation tool with no output schema, the description is sparse: it doesn't mention duplicate behavior, idempotency consequences, error conditions, or how member types map to parameters. The schema partially compensates by listing the member-type arrays, but the overall tool definition leaves important operational context implicit.

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 the baseline is 3; the description itself contributes no parameter details. The schema's Russian descriptions for the member-ID arrays are meaningful, but accessGroupId is only described as 'integer (required)', which is a tautology rather than a semantic explanation.

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 states a specific action ('Add members') on a specific resource ('an access group'), which clearly distinguishes it from sibling tools like AccessGroupsCreate, AccessGroupsDelete, and AccessGroupsGetDetails. However, it does not enumerate member types such as teachers, group classes, or individual classes, leaving some purpose detail to the schema.

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?

No guidance is provided on when to use this tool versus alternatives such as AccessGroupsRemoveMembers or AccessGroupsCreate. The description gives no selection criteria, no recommended conditions, and no exclusions or prerequisites.

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