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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds the shape of what is returned (packages per platform, templates, screens/services/events/data models), but says nothing about lookup failure, missing names, or payload size.

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?

One dense sentence that front-loads the verb and resource, then enumerates the returned contents. No filler and nothing redundant with the schema or annotations.

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?

With no output schema, the description takes on the burden of explaining the return value and does so by enumerating the workflow's constituent parts. It falls slightly short by not indicating error behavior for an unknown workflow name or how the nested reference architecture is structured.

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?

There is a single 'name' parameter with 100% schema description coverage including concrete examples (local-handoff, backend-delivery). The description adds no extra syntax or semantics beyond the schema, so the 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?

States a specific verb (get) and resource (one workflow) and enumerates the payload contents: capabilities, packages per platform, starter templates and reference architecture. It is clearly distinct from list_workflows/search_workflows by implication, but never explicitly contrasts itself with sibling getters like get_package or get_skill.

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?

The phrase 'Get one ... in full' implies usage when the full workflow definition is needed rather than a search or list, but there is no explicit statement of when to use this tool versus the 14 siblings, nor any prerequisite or exclusion. Usage is left to inference.

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