add_space_members

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

Description claims idempotency ('Idempotently add members'), but annotation idempotentHint is false—a direct contradiction. Additionally, 'replacing the full members array' implies destructive behavior (removing members not in list), yet destructiveHint is false. This misalignment undermines transparency.

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?

One sentence covering purpose, idempotency, input format, and behavior. It is front-loaded and efficient. Could be slightly more concise but effective.

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?

Covers key behavior (idempotent, resolution, full replacement) but lacks details on permissions, prerequisites, error scenarios, or output. Output schema exists, so return values are documented elsewhere. However, the important side effect of removing unlisted members is not explicitly stated.

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?

The description adds value by explaining that members accept UUID, email, or display name and are resolved to account UUIDs. Schema descriptions are generic ('a string that will be trimmed'), so the tool description enriches parameter understanding. The member parameter is well-described in both schema and description.

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 members to an existing Huly space and mentions idempotency. It distinguishes from siblings like remove_space_members, but does not explicitly contrast with add_space_role_members or 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 explicit guidance on when to use vs alternatives (e.g., add_space_role_members). Does not mention preconditions (space must exist, permissions) or when not to use. Implied usage is present but minimal.

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