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

The description adds a clear side-effect statement: none, beyond minting a handle and writing no state. This supplements the readOnlyHint and destructiveHint annotations, which align with the described behavior.

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 description is short, front-loaded with the core purpose, and uses a separate line for side effects. Every sentence adds operational value with no redundancy.

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 parameters, an output schema present, clear sequencing instructions, and side-effect disclosure, an agent has everything it needs to invoke this tool correctly.

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 has zero parameters, so the schema covers everything. The description does not need to document inputs; mentioning the returned pipeline_id is sufficient for invoking subsequent tools.

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 action ('Starts a new pipeline'), identifies the resource, and names the key output (pipeline_id). The fax context and 'call this first' framing clearly distinguish it from the many sibling tools.

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 instructs the agent to call this first when sending a fax, pass the returned id to every subsequent pipeline tool, and optionally use it with list-numbers/list-contacts. This provides exact sequencing and routing guidance.

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