get_workflows

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

readOnlyHint=true in annotations already establishes this is a safe read, so the description carries a lighter burden. 'Of the organization' adds the useful nuance that there is no queue/user scoping, but nothing is said about pagination, result caps, or ordering — meaningful gaps for a list endpoint with no output schema.

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?

A single short sentence, front-loaded with the verb and resource, with no filler or repetition. It is efficient, though its brevity leaves scope and return behavior unaddressed.

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?

With no output schema, no pagination cues, and siblings that suggest paginated variants exist (get_boards_paginate), the description does not say whether results are paginated, capped, or what a workflow record contains. For a bare list endpoint this leaves the agent under-informed about what to expect back.

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 tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify or compensate for regarding inputs. No parameter-related gaps exist by construction.

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 clear verb and resource ('List all workflows') with an organization-level scope, so the basic purpose is legible. However, it does not distinguish itself from the singular sibling get_workflow, the queue-scoped get_queue_workflows, or create_workflow/update_workflow, so an agent must infer which listing tool to pick. Accurate but not distinguishing.

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?

No when-to-use guidance at all: nothing says when to call this versus get_workflow or get_queue_workflows, and no exclusions or prerequisites are given. Usage must be inferred entirely from the name.

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