set_space_owners

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

Adds beyond annotations by stating default membership behavior. No contradiction with idempotentHint. Does not detail authentication or side effects, but annotations already cover readOnly/destructive hints.

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?

Two concise sentences covering purpose, param types, and default behavior without fluff. Efficient use of words.

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 main points for a mutation tool with output schema. Could mention complete replacement of existing owners, but overall adequate.

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?

Adds significant meaning: owner identifiers can be UUID, email, or name; clearing owners with []; ensureMembers defaults to true. Schema coverage is 100%, but description enriches beyond basic descriptions.

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?

Description clearly states 'Replace owners on an existing Huly space' with specific verb and resource. It distinguishes from siblings like add_space_members and set_space_role_members by focusing on owners.

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?

Implies usage through phrase 'By default, owners are also ensured in members' but gives no explicit when-to-use or alternatives. Lacks exclusions for when not to use.

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