Add participant

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds that the operation targets a single conversation and exposes the underlying REST endpoint, but it does not disclose required permissions (e.g. moderator rights), what happens when the participant already exists, or whether guests receive an invitation.

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 with the action front-loaded; nothing is padded. The trailing raw endpoint line is of marginal value to an agent and slightly dilutes the structure, but it is brief.

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 three-parameter mutation with annotations present and no output schema, the definition covers the core action but omits permissions, duplicate-participant behavior, and failure modes. An agent could call it, but would be guessing about prerequisites and edge cases.

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%, so the description must compensate, and it partly does: the four source kinds (user, group, email guest, team) map onto the 'source' enum values users/groups/emails/circles. However, it never explains the 'token' parameter's meaning or the expected format of 'participant' (user ID vs email address).

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 gives a specific verb plus resource ('Add a user, group, email guest or team to one conversation'), which clearly distinguishes it from siblings like nextcloud_list_participants and nextcloud_remove_participant. The scope ('one conversation') is stated, though it never names the sibling tools it complements.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are referenced despite list/remove participant siblings existing. The usage is only implied by the verb and the mention of 'one conversation'.

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