Remove participant

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that — it omits the consequences of removal (whether the user is ejected from the conversation, what happens to their messages), the permission level required, and the confirmation behavior.

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 lines, front-loaded with the action and the id source, with no filler prose. The raw REST endpoint is arguably redundant with the annotations but takes minimal space.

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?

For a destructive, three-parameter mutation with no output schema, the definition covers identity and the id source but leaves the confirm workflow, required permissions, and post-removal effects unstated. Adequate to invoke, thin on decision-relevant context.

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?

With only 33% schema coverage, the description compensates partially by explaining where attendee_id originates. But 'token' is only inferrable from the pasted endpoint URL, and the 'confirm' parameter — the one field the schema documents — is never referenced in the description, leaving the destructive-confirmation workflow unexplained.

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 ('Remove one attendee ... from a conversation'), which cleanly separates it from nextcloud_add_participant and nextcloud_list_participants. The appended raw DELETE endpoint adds little for an agent and slightly dilutes an otherwise crisp one-sentence purpose.

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?

Provides a genuine prerequisite: the attendee_id must come from list_participants, which tells the agent how to sequence the call. However, it gives no when-not guidance (e.g. removing vs deleting a conversation, or how this differs from remove_user_from_group) and never mentions the counterpart add_participant.

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