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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low; the description adds that it returns workflow IDs, descriptions, required inputs and tools, and that personal skills are included with source personal and my- IDs. The "Read-only; creates no projects or media" clause largely restates the annotations, which is why this is a 4 rather than a 5.

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?

The long outcome list is front-loaded and directly serves semantic matching, so it earns its space. The closing read-only sentence duplicates the annotations and could be trimmed without loss.

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 compensates by describing the return payload (IDs, descriptions, required inputs, tools) and by flagging that personal skills appear with distinctive ID prefixes. An agent can select, call, and route to the next step correctly from this text alone.

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 tool takes no parameters, so there is nothing the description needs to disambiguate beyond confirming it is an unfiltered discovery call. Baseline for a zero-parameter schema is 4.

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 ("Find workflows") and enumerates the concrete outcomes it covers, from walkthroughs to reframing. It is clearly distinguishable from the sibling get_sequencer_skill, which is named as the loading step rather than the discovery step.

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?

Gives an explicit when-to-use rule: "Use for these outcomes even when the request does not name Sequencer," which preempts the most likely selection failure (agent skips it because the user never said Sequencer). It also names the follow-up alternative explicitly: "Load the selected workflow with get_sequencer_skill."

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