add_channel_members

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

The description claims idempotent behavior, but the annotation sets idempotentHint to false, creating a contradiction. Additionally, the phrase 'replacing the full sorted member array' conflicts with the tool name 'add', suggesting it may function as a set operation rather than additive. No additional behavioral context (e.g., auth requirements, side effects) is disclosed.

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 dense sentence that conveys all essential information efficiently. It is not overly wordy, but could be slightly more structured with front-loaded key action and constraints.

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?

The description covers the main action and resolution behavior, and the schema and output schema provide ample structural info. However, it omits error cases, permissions, and contradicts the idempotency annotation. Given the complexity, it is adequate but not fully comprehensive.

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 schema already provides good descriptions for both parameters (channel and members), achieving 100% coverage. The description adds value by explaining that member values can be UUID, email, or display name and are resolved before replacing the array. This clarifies usage beyond the schema.

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 verb 'add', the resource 'members to a non-archived Huly channel', and includes constraints like idempotency. It distinguishes from the sibling 'remove_channel_members' by specifying the action. The purpose is specific and unambiguous.

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 the tool (adding members to a non-archived channel) but does not explicitly state when not to use it or mention alternatives beyond the sibling. No exclusions or prerequisites are provided, leaving some ambiguity.

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