add_space_role_members

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

Annotations already indicate idempotentHint=true. The description adds 'preserving all other role assignments', which is useful but not extensive. It does not disclose what happens if the role doesn't exist or if members are already present, leaving some behavioral gaps. No contradiction with annotations.

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 with no fluff. The first sentence states purpose and key behavior (idempotent, preserving assignments), and the second explains parameter formats. Every word earns its place.

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?

Given the tool has 5 parameters, 3 required, and an output schema exists (not shown but indicated), the description covers idempotency, parameter formats, and behavioral nuance. Minor gaps like error handling are acceptable. Overall complete for a tool with good annotations.

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%, baseline 3. The description adds significant value by specifying that 'role' accepts a raw role _id or exact role name, and 'members' accept UUID, email, or display name. This clarifies acceptable formats beyond the schema's generic 'a string that will be trimmed'.

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's purpose: idempotently adding members to one role on a typed Huly space while preserving other assignments. The verb 'add' and resource 'members to one role' are specific, and it distinguishes from sibling tools like remove_space_role_members and set_space_role_members.

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. There is no mention of prerequisites, when not to use it, or any comparison with similar tools like add_space_members. The description is self-contained but lacks any usage context.

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