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

Goes well beyond the annotations by disclosing the key behavioral trait: the workflow is persisted as an inactive draft and nothing sends until activation plus owner enrollment. With annotations already declaring non-destructive, non-idempotent write behavior, this is the extra context that matters. It doesn't cover what is returned or duplicate-name handling.

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?

Three tight paragraphs: the draft-status constraint is front-loaded, template sourcing second, and a single worked example last. Every sentence carries actionable information and none is filler.

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?

For a mutating tool with no output schema, it covers lifecycle, template prerequisites, and the branch limitation. The notable gap is that it never says what creation returns (e.g. a workflow id needed to call spur_set_workflow_active or spur_enroll_owners_in_workflow).

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 coverage is 100%, so baseline is 3, and the description earns above that by giving a concrete steps example and by mapping each step type to its correct template source (spur_list_message_templates vs. postcard/letter templates). It adds real meaning about step ordering and composition beyond the schema.

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 ('create a multi-step outreach sequence from saved templates') and immediately distinguishes it from the related siblings that activate it (spur_set_workflow_active) and enroll owners. An agent can tell this builds a draft sequencing object rather than sending anything.

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?

Clearly says when to use it (building a send/wait sequence) and notes the prerequisites: templates must exist first, and reply/open/click branches cannot be created here and must be added in the UI afterwards. It does not distinguish this from the adjacent spur_create_search_automation approach or single-send tools, which is the remaining routing gap.

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