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 usefully discloses the payload shape (pipelines plus their stages) and the underlying FUB endpoint GET /v1/pipelines, but says nothing about ordering, pagination, or whether the name filter is exact-match server-side.

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 compact clauses, front-loaded with the resource and with zero filler; the parenthetical about downstream stage ids earns its place. It is slightly telegraphic, reading as fragments rather than full sentences.

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 list tool with full schema coverage and no output schema, the description covers what it returns and why it matters, which is most of the job. It omits any indication of result volume or pagination and never addresses the name filter, leaving small gaps relative to a one-param tool.

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% for the single optional 'name' parameter, so the schema already documents it. The description adds no information about the filter's matching behavior, which leaves the baseline of 3.

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 names the resource (deal pipelines) and, unusually, pre-answers the follow-up question by explaining that the embedded stage ids are what fub_create_deal / fub_update_deal consume. It is a clear noun phrase rather than an explicit verb+resource sentence, and it does not distinguish itself from the sibling fub_list_stages, which overlaps in subject matter.

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?

It implicitly defines the use case: fetch this when you need stage ids to pass into create/update deal calls, naming the exact downstream tools. There is no explicit 'when not to use' or steering away from fub_list_stages, so it stops short of the top band.

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