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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveness, so the safety profile is carried structurally. The description adds one genuinely useful behavioral fact beyond that: picking a template does not execute anything. It omits other relevant behavior such as what a returned entry looks like, whether results are paginated or ordered, and whether permissions gate company-owned templates.

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 capability statement front-loaded and no filler. The second sentence is terse to the point of being cryptic, which costs a little clarity but nothing is wasted.

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 three-parameter list tool with zero schema descriptions and no output schema leaves the description responsible for return shape and filter semantics, and it delivers neither. An agent can call it, but cannot predict what comes back or how 'retired' affects the result set.

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?

Schema description coverage is 0%, so the description must compensate and largely doesn't. 'Company/environment-owned' loosely signals that company and environment scope the results, but the retired flag is never mentioned and an agent has no way to know it toggles inclusion of retired templates versus filtering them out.

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 the verb (read) and the resource precisely: built-in tasks plus company/environment-scoped workflow templates. It is distinguishable from write-side siblings like summer_workflows_save or summer_workflows_request_text, though it never names those siblings explicitly. The conflation of 'tasks' and 'templates' in one phrase slightly muddies what is actually listed.

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?

There is no statement of when to use this versus siblings such as summer_workflows_history, summer_workflows_save, or summer_workflows_request_text. 'Selecting one never runs work' reassures about side effects but is not usage routing; the agent must infer that this is the browse/discovery step before invoking or requesting a workflow.

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