b24_read_pipelines

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

No annotations are provided, so the description carries the behavioral burden. It communicates the read-only nature through the verb 'Lee' and enumerates the included data (stages, colors, semantics, order). However, it does not mention return format, pagination, or authentication requirements, which would add useful transparency for a tool with no annotation coverage.

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, front-loaded sentence that starts with the action and resource, then lists the relevant attributes. Every word earns its place and there is no redundancy or 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?

With no output schema, the description names the returned resources and their distinguishing attributes, making the tool's output reasonably clear. The optional parameters and defaults are fully covered by the input schema. Minor gaps like pagination or explicit response structure are acceptable given the tool's simplicity.

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%, and both parameters are documented with clear optional/default semantics. The tool description adds no additional meaning for webhook_url or entity_type_id, so it does not exceed the schema's baseline contribution.

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 'Lee' (reads) and a specific resource 'pipelines (funnels)'. It further clarifies what is returned: stages with colors, semantics, and order. This clearly distinguishes it from sibling read tools like b24_read_entity_types or b24_read_custom_fields.

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 tool should be used when pipeline/funnel definitions and stages are needed, but it does not provide explicit guidance about when not to use it or how it compares to alternative tools. The resource is clear enough for basic inference, but no exclusions or sibling routing are mentioned.

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