get_pipelines

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It does not indicate return format, pagination behavior, permission requirements, or whether 'all' refers to all accessible pipelines globally or within a specific scope.

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 extremely brief at three words. While it wastes no words, it is insufficiently sized for the tool's complexity given the sibling context and lack of output schema. However, the structure itself is appropriately concise.

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?

Given the presence of a singular variant sibling tool ('get_pipeline') and the absence of an output schema, the description should clarify the scope of 'all' and hint at return structure. It fails to provide necessary context for safe and 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?

The input schema contains zero parameters. Per evaluation guidelines, tools with 0 parameters receive a baseline score of 4, as there are no parameter semantics to clarify beyond what the empty schema already conveys.

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 'Get all pipelines' is essentially a tautology that restates the tool name. While it indicates the tool retrieves multiple items, it fails to distinguish from the sibling tool 'get_pipeline' (singular) or clarify what constitutes a pipeline in this CRM context.

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?

No guidance provided on when to use this tool versus the singular 'get_pipeline' or other filtering tools. There are no stated prerequisites, constraints, or conditions that would help an agent select this over alternatives.

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