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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world behavior, so the safety profile is covered. The description adds genuine scope context beyond that: authentication, authorization, storage and deployment are host responsibilities described by the manifest, telling the agent what this call will not do. It still says nothing about size limits, pagination, or whether source files are inlined or referenced.

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 tight sentences with zero filler. The primary action and return payload are front-loaded, and the scope disclaimers follow as supporting context.

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?

An output schema exists, so the description needn't enumerate return fields, and the annotations cover the safety profile. Combined with a 100%-covered parameter schema, the definition is nearly complete; only a cross-reference to sibling tools for related lookups is missing.

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 single 'id' parameter has 100% schema description coverage including an example, so the schema carries the semantics. The description reinforces that exactly one workflow is returned (hence a singular id), but adds no format, resolution, or lookup-detail beyond the schema; baseline 3 applies.

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 description uses a specific verb ('Return') and names the resource precisely ('one bundled workflow manifest and its source files'), which clearly contrasts with the plural listing sibling list_workflows. It does not, however, explicitly name or distinguish itself from get_component or get_guide, so differentiation is implied rather than stated.

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 implied by the singular 'one bundled workflow' phrasing, which signals a single-item fetch by ID as opposed to the sibling list_workflows. There is no explicit when-to-use statement, no prerequisites, and no routing advice toward get_component or search_components for related lookups.

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