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

readOnlyHint=true already tells the agent this is a safe read, so the description's marginal value is limited to the 'applies to every member' scope note. It says nothing about ordering, pagination, whether gym-wide and per-member workflows are returned together, or how results relate to list_workflows.

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?

Zero waste and front-loaded, but it is a single sentence fragment rather than a complete sentence, and its brevity comes at the cost of the information an agent needs. Conciseness is fine; structure is thin.

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?

A one-parameter read with no output schema should still disclose what the listing contains and its shape (e.g., whether paginated), especially given a dense sibling set of workflow tools. The description leaves the agent guessing about result content and how it differs from list_workflows in practice.

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?

Only one parameter (organizationId) and schema description coverage is 100%, with a cross-reference to list_my_organizations already in the schema. Baseline 3 applies — the description adds no syntax or sourcing detail beyond the 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 fragment identifies the resource (gym-wide workflows) and adds a useful scope gloss — they apply to every member of the gym — which distinguishes it from list_workflows. But it never states the verb: an agent must infer from the name that this lists them, and the fragment alone would not read as a description of an action.

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 indication of when to call this versus the many obvious alternatives in the sibling list (list_workflows, list_workflow_templates, list_workflow_runs, list_gym_workflows' create/update/delete counterparts). The parenthetical hints at scope but gives no triggering condition or exclusion.

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