ghl_pipelines_get

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

No annotations are provided, so the description carries the full burden. It states the primary action but does not disclose details such as return format, error behavior, or whether pipeline stages are included. Since it is a simple read-only operation and the description is not misleading, it meets the minimum but lacks extra behavioral context.

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 a single, direct sentence with no redundant words. It conveys the purpose instantly and is appropriately sized for a simple tool, earning full marks for conciseness.

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 simple listing tool with one parameter and no output schema, the description sufficiently conveys that all pipelines for a location will be returned. It does not detail the response structure, but the phrase 'get all pipelines' is adequate for a basic read operation, and the sibling tools clarify the pipeline tool family.

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 description coverage is 100% with a clear explanation of locationId, including the fallback to GHL_LOCATION_ID. The tool description adds little beyond the schema, simply reaffirming the location scope. With complete schema coverage, a baseline of 3 is appropriate.

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?

The description uses a specific verb 'Get' and identifies the resource 'all pipelines' with a location scope, clearly distinguishing it from sibling tools like ghl_pipeline_get. It fully states what the tool does in a precise and unambiguous way.

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 provides clear context: use this tool when you need all pipelines for a location. It does not explicitly name alternatives or exclusions, but the plural 'all' implies separation from single-pipeline retrieval. This is clear context without explicit alternatives, scoring a 4.

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