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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the underlying GET /Pipelines endpoint and the shape of what comes back, but says nothing about pagination limits or ordering beyond what the schema's top/skip fields imply.

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 short sentences, front-loaded with the resource and the return fields. Nothing is wasted; the endpoint reference is a compact addition for integrators.

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 compensates by naming the fields returned, which is the essential information for a lookup tool. It is complete enough to call correctly, though paging behavior is left entirely to the schema.

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%, so both parameters (top, skip) are fully self-documented with ranges and defaults. The description adds no paging guidance beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("List the sales and project pipelines") and enumerates the returned fields (PIPELINE_ID, name, opportunity vs project). It is naturally distinct from the sibling insightly_list_pipeline_stages, though it never explicitly routes the agent between the two.

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?

Usage is only implied: as a read-only list of reference data, it is obviously the lookup call an agent would make before creating an opportunity. There is no explicit when-to-use, when-not, or mention of the adjacent insightly_list_pipeline_stages / insightly_list_lead_sources tools.

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