List participants

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered externally. The description's only added content is the raw REST endpoint, which confirms it is a plain read but says nothing about pagination, participant record shape, or whether group/conversation members are included.

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 with the purpose front-loaded and no filler. The raw endpoint line is compact and mildly informative rather than wasteful, though it adds less value than a sentence about return contents would.

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?

This is a simple read-only tool with one required parameter, and the annotations fully cover its safety behavior, so the minimal description is close to adequate. The remaining gap is that with no output schema and no parameter descriptions, nothing tells the agent what a participant entry contains or how the token is sourced.

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 0% for the single 'token' parameter, so the schema alone does not explain it. The URL path '/room/{token}/participants' implicitly ties the token to a conversation/room, which is genuine added meaning, but it never states format or where to obtain the token.

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 ('List the participants') scoped to 'one conversation', which is far better than the tautological title alone. It does not, however, distinguish itself from nearby siblings such as nextcloud_list_conversations or nextcloud_get_conversation, so an agent must infer the boundary.

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 gives no when-to-use guidance and names no alternative. It never says to call nextcloud_get_conversation first for context or to use nextcloud_add_participant/nextcloud_remove_participant for membership changes, leaving routing to the agent's inference from the name.

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