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

Annotations already establish the safe read-only, idempotent profile, but the description adds genuinely non-redundant behavior: the payload is advisory ('suggested steps, not commands'), no schedule executes server-side, and consent is required before creating anything recurring. It also flags that scheduling requires offering xTiles notifications, which is an operational trait the agent could not infer from `readOnlyHint`.

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?

Purpose is front-loaded in the first clause, and each subsequent sentence carries a distinct instruction rather than filler. It runs long for a single-parameter read tool, and the scheduling/notification guidance is slightly tangential, but nothing is redundant enough to waste the agent's attention.

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?

The tool has an output schema, so return-shape detail is unnecessary, and the description correctly focuses on how to interpret and act on the output instead. Given the low structural complexity (1 param, no nesting) it covers everything an agent needs to call it and use the result responsibly.

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?

One parameter with 100% schema description coverage — the schema already explains that the id must match a value from `xtiles_list_workflows` and gives an example. The description restates the discovery path without adding format or constraint detail, 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 and resource ('Fetch a prepared xTiles workflow by id') and then defines the resource in terms of what the agent will actually receive ('a recipe the xTiles team wrote for this kind of request'). This is enough to distinguish it from the sibling `xtiles_list_workflows`, which is named as the discovery path.

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?

Explicitly routes the agent: call `xtiles_list_workflows` first to discover ids, then treat the returned Markdown as reference material rather than executable commands, and adapt or skip steps. It also gives a decision rule for the awkward case (recurring recipes → ask the user before setting anything up), which is exactly the kind of when/when-not guidance that prevents misuse.

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