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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds the API endpoint (GET /Pipelines) and the shape of the returned records (PIPELINE_ID, name, opportunities vs projects), which partially compensates for the absent output schema, but discloses nothing about auth, rate limits, or paging behavior.

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?

One sentence plus a short endpoint reference; the key content (what is listed and what fields come back) is front-loaded with no filler. The endpoint citation is marginal but not padding.

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, read-only, two-parameter list call with no output schema, the description supplies enough: the resource, the returned field names, and the underlying endpoint. Only paging semantics and the absence of filtering go unaddressed, which the schema largely covers.

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 both top and skip fully documented in the schema (including the API default of 100), and the description does not repeat or extend them. Baseline 3 is appropriate when the schema carries the parameter burden.

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 pairs a specific verb (List) with a specific resource (sales and project pipelines) and enumerates the fields returned, which implicitly separates it from the similarly named insightly_list_pipeline_stages. It never explicitly names that sibling, but the resource is unambiguous.

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: an agent can infer this is the reference-lookup call for pipeline IDs before creating opportunities or projects, but the description states no when-to-use condition, no exclusions, and no alternative. With no filtering parameters, there is little routing guidance to give.

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