mirlo_list_pipelines

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

No annotations are provided, so the description must stand alone. It describes a read-only listing operation without mentioning destructive effects or authentication needs. While it is clear that it retrieves data, it does not explicitly state the non-destructive nature or any behavioral traits beyond the listing.

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?

Two concise sentences with no redundant information. The purpose is front-loaded, and every word contributes to clarity.

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 zero-parameter list tool with no output schema, the description adequately explains what it returns (pipelines with stages and IDs) and why it is useful. However, it does not specify the exact structure or field names of the output.

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?

There are no parameters, so baseline is 4. The description adds meaning beyond the schema by explaining the purpose (getting pipeline/stage IDs for deal creation) and the output content (pipelines with stages), which helps the agent understand what will be returned.

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?

Clearly states it lists all pipelines with their stages, using a specific verb and resource. Distinguishes itself from sibling list tools by focusing on pipelines, and provides a concrete use case for getting IDs before creating deals.

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 mentions that it is useful before creating deals, which gives clear context for when to use it. However, it does not provide explicit when-not-to-use instructions or alternatives, though the use case is well implied.

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