get-project-workflow-list

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

Annotations already cover readOnly, idempotent, and openWorld, so the safety profile is known. The description adds real context beyond that: the four workflow classes with bilingual labels, the fact that projects may have custom workflows, and the return shape (id, name, order, class). Missing only notes on pagination or error 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?

Front-loaded with the core purpose, then the class taxonomy, then actionable URL guidance and return shape. The taxonomy list is long but earns its place because class semantics matter for interpreting results; no filler sentences.

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?

There is no output schema, so the description's 'Returns: Array of workflows with id, name, order, and class' is necessary and present. The tool is simple (one parameter), and the description covers purpose, input derivation, and output shape adequately.

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 100% schema coverage the single projectId parameter is documented, giving a baseline of 3. The description goes further by explaining how to extract projectId from a Dooray URL ('/task/PROJECT_ID') and giving a concrete example value, which the schema does not convey.

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 ('Get list of workflow statuses for a project') plus the domain meaning of workflows. No sibling tool retrieves workflows, so the agent can select it unambiguously.

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?

Explicitly says to use the returned workflow IDs when calling create-task or update-task, naming the alternative tools and the downstream context. The URL pattern section additionally tells the agent how to obtain the required projectId from a Dooray URL.

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