huddo_transfer

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

With no annotations, the description carries the full behavioral burden and does well on the two most important facts: it requires owner privileges, and the caller is demoted to a regular member rather than removed ('You stay in it as a member'). It omits failure modes (target not a member, invalid room) and whether the transfer is reversible.

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 short sentences, the permission gate front-loaded before the action, and the post-state consequence last. Every clause carries information and there is no filler.

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?

No output schema and no annotations, so the description must stand alone, and it covers purpose, authorization, and the resulting state change. For a single-required-parameter tool this is close to sufficient; error conditions and reversibility are the remaining gap.

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 description coverage is 100%, so the schema already documents 'as', 'to', and 'room' with defaults. The description only echoes the 'to' parameter's accepted forms and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: transfer room ownership to another member. It is clearly distinguishable from siblings like huddo_kick (removal), huddo_invite (adding), and huddo_leave (self-exit), and the '(slug or display name)' hint identifies the target argument form.

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 precondition 'Owner only' tells the agent exactly when this tool is callable, which is meaningful routing information. It stops short of naming an alternative action for non-owners or the case where the target is not a member, so it is clear context without explicit alternatives.

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