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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, so safety is covered. The description adds useful context that these are copyable prebuilt templates, but says nothing about how results are filtered or whether the full catalog is returned when query is omitted.

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 sentences, zero filler, with the resource scope front-loaded and the follow-up action second. The parenthetical examples earn their space by anchoring what 'template' means.

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 one-parameter read tool with full schema coverage and no output schema, the definition is nearly sufficient. The one meaningful gap is that it never states what the listing returns (names, ids, descriptions) — an agent needs to know it gets an identifier it can hand to create_workflow_from_template.

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 description says nothing about the query parameter or that the catalog is fuzzy-searchable; that work is done entirely by the schema, which is at 100% coverage and gives examples and omission guidance. With the schema fully documented, the baseline of 3 applies — nothing is added, but nothing is contradicted.

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+resource ('List the prebuilt workflow templates') and enumerates concrete examples (purchase order, invoice, time off, vendor onboarding, access request), which makes the catalog scope tangible. It does not distinguish itself from describe_workflow_template or list_workflows, so sibling differentiation is only partial.

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?

'Use before create_workflow_from_template' gives an explicit sequencing rule that tells the agent when this tool belongs in a flow. It offers no when-not guidance and never mentions describe_workflow_template as the alternative for inspecting a single template's details.

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