Get Flow project participants

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only operation ('retrieves'), but it does not disclose authentication requirements, pagination, rate limits, or the structure of the returned participants. The description is minimal and adds only the read intent, lacking substantive behavioral context.

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 that gets to the point without unnecessary words or repetition. It is appropriately front-loaded with the action and resource. However, it is arguably under-specified, which slightly detracts from its effectiveness, but as a concise statement it is well-structured.

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?

Given the tool's simplicity (a read operation) and the lack of an output schema, the description is insufficient for an agent to fully understand the invocation context. It does not describe the return format, potential errors, or the significance of the parameters. The complete absence of parameter semantics and behavioral details leaves significant gaps.

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%, and the description does not compensate by explaining any parameters. It mentions project participants, hinting at projectId's role, but it does not clarify the purpose of apiKey or baseUrl, nor the format of projectId. With three parameters and no description coverage, the agent receives no added semantic value beyond the raw schema.

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 tool retrieves a list of project participants for a Flow project. It uses a specific verb ('조회합니다' - retrieves) and identifies the resource (project participants), which is understandable and distinct from sibling tools like list_projects or get_project_columns. However, it does not explicitly differentiate from list_participant_projects, so it misses the top score.

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. There is no mention of context, prerequisites, or exclusions. It simply states what the tool does without any usage direction, so the agent must infer applicability from the name and description.

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