Set Tree Members

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

While annotations confirm it is not destructive, the description provides high-value operational transparency. It explicitly states that no person is copied, relationships are maintained/visible within the tree scope, and that removing membership preserves global records.

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 dense and manages multiple pieces of information efficiently. Although not aggressively short, every sentence serves to clarify scope, input source, or behavioral guarantee.

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 is highly complete for a complex membership management tool. It covers the source of the IDs, the scope of the operation (tree vs. all), and the persistence of relationships, addressing most potential ambiguities.

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?

Given the low schema coverage (33%), the description is vital for understanding parameter usage. It clarifies that the 'tree' parameter accepts either a stable UUID or the exact name derived from the `list_trees` tool, adding critical semantic context to the UUID/Name choice.

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 defines the dual purpose: adding members or removing membership. It successfully differentiates this tool from others by specifying that it operates on 'existing collection people' and handles relationship visibility within the tree.

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?

It provides critical procedural guidance regarding parameter input. Specifically, it instructs the agent to reuse UUID identifiers obtained from the `find_people` sibling tool and specifies the condition under which the `tree` UUID can be omitted (to search all people).

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