Add Flow project participants

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action ('adds participants') without explaining side effects, idempotency, whether existing participants are overwritten, authorization needs, or what happens on error. This is a significant transparency gap for a mutation tool.

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?

The description is a single, concise sentence with no filler. It is front-loaded and easy to read. However, it is extremely brief and essentially restates the title, so while it is efficient, it does not add substantive value beyond the title itself.

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 tool with 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns (if anything), how to handle errors, or the relationship between registerId and participants. The moderate schema descriptions are not enough for an agent to confidently invoke the tool correctly in varied situations.

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?

The description adds no parameter semantics beyond the schema. Schema coverage is 60% (3 of 5 parameters have minimal labels such as 'project ID' or 'participant info'), but the description does not clarify the role of 'registerId' (writer ID) or how it differs from 'participantId'. It also ignores apiKey and baseUrl, leaving their purpose undocumented.

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 clearly states the function: 'Adds participants to a Flow project' (Korean). It uses a specific verb ('adds') and a specific resource ('participants to a Flow project'), which fully distinguishes it from sibling tools like get_project_participants that handle retrieval. The title reinforces this, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention conditions like 'use when you need to add participants', nor does it reference any prerequisites, limitations, or exclusions. The use case is only implied by the function itself, not explicitly stated.

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