parse_add_users_to_role

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

With no annotations provided, the description carries the full burden. It discloses important behavioral traits: the operation requires the master key, the role must exist, and users inherit the role's permissions. This goes beyond a simple mutation statement and helps the agent understand side effects and prerequisites.

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 sentences, front-loaded with the action, and every word adds value. It avoids unnecessary detail while covering the action, effect, and a critical prerequisite.

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 two parameters and no output schema, the description provides the essential purpose, prerequisite, and behavioral effect, which is sufficient for an agent to select and invoke it correctly. It does not mention idempotency or error handling, but those are not critical for initial tool selection.

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?

Although the schema has 0% description coverage at the top level, the description clarifies the meaning of the parameters: 'objectIds' refers to user IDs and the role is identified by its objectId. This compensates for the sparse schema and gives the agent enough semantic information to map inputs correctly.

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 clearly states the tool adds one or more users to an existing role via objectIds, which is a specific action distinct from sibling tools like parse_remove_users_from_role. It also notes the permission inheritance effect, reinforcing its purpose.

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 implies when to use this tool (to grant role permissions to users) and provides context such as the requirement that the role already exist and that master key is required. It does not explicitly mention alternatives or exclusions, but the clear purpose and sibling list make usage boundaries evident.

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