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

Annotations flag destructiveHint=true and openWorldHint=true, and the description goes beyond them by disclosing the real-world consequence: the workflow begins emailing/texting/mailing on its schedule and consumes credits. It omits details like what happens to owners already enrolled or how credits are counted, but the core side-effect disclosure is strong.

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 short sentences, no filler. Purpose first, then the consequence (outreach + credits), then the confirmation requirement — properly front-loaded.

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 a fully described 3-param schema, annotations covering safety, and no output schema, the description covers purpose, cost implication, and the confirmation gate. It leaves minor gaps around partial-failure behavior and duplicate enrollment, but nothing critical for correct invocation.

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% and the schema itself documents owner_ids provenance, skipping of owners lacking contact details, and the confirm gate. The description only restates 'workflow name and owner count' for confirmation, adding little semantic value 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?

Clear specific verb+resource: enrolls owner records into an outreach workflow, which is distinguishable from sibling mutations like spur_set_workflow_active or spur_create_workflow. It does not explicitly name a sibling to contrast with, keeping it short of a 5.

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 description implies the right context (after selecting a workflow and finding owners via spur_find_owners) and adds a prerequisite to confirm the workflow name and owner count with the user first. It gives no explicit when-not guidance or alternatives to this tool.

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