bdesign_workflow_template_list

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still adds real value by preempting a plausible confusion with the sibling apply/preview tools ('Reading does not instantiate or run them'). It does not address what the listing returns or how it is ordered, but for a no-param read that gap is modest.

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?

Two short sentences with the scope-restricting clause front-loaded and the side-effect disclaimer immediately after. Nothing is redundant or padded.

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 parameterless read tool with a readOnlyHint annotation and no output schema, the description supplies what matters: what is listed, where from, and that listing has no side effects. Only the shape/contents of the returned template entries is unaddressed, which is a minor omission given the low complexity.

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, which is the baseline-4 case, and the schema is trivially complete (additionalProperties false, 100% coverage). The description adds no parameter meaning because none exists to explain.

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 pair ('List reusable workflow templates') plus a scope qualifier ('in this local installation') that helps distinguish local templates from any remote/shared ones. The plural 'list' form inherently separates it from bdesign_workflow_template_get, preview, and apply, though no sibling is named explicitly.

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?

Usage is only implied: the tool is for browsing templates, and the note that reading does not run them hints that bdesign_workflow_template_apply is the execution path. There is no explicit 'use this when you need X, use apply instead when Y' statement, so the agent must infer the routing.

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