Get Pipelines

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the auth scope 'opportunities.readonly', which is useful context beyond annotations, but it does not describe response behavior, pagination, or any other side-effect-relevant details.

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 compact and front-loads the core action and endpoint. The 'Scopes' line is useful and there is no filler, though the phrase 'Get Pipelines' partially duplicates the title without adding much information.

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?

The tool is simple, but with no output schema and no parameter explanation, an agent lacks important calling context. The annotations cover safety but not what the response contains, how locationId should be sourced, or what makes this tool distinct among related opportunities tools.

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 0%, and the description gives no meaning for the sole required parameter 'locationId'. While the parameter name is somewhat self-explanatory, the description contributes nothing to clarify what value should be passed or how it affects the request.

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 states a specific verb and resource ('Get Pipelines') and includes the HTTP endpoint and required scope, making the basic purpose unambiguous. It does not explicitly differentiate it from sibling opportunity tools, but 'pipelines' is a distinct resource among the listed siblings.

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?

There is no guidance on when to use this tool versus the many sibling tools. It does not say 'use this to list pipelines before creating an opportunity' or when the alternatives like opportunities_search_opportunity would be more appropriate.

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