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

Annotations already declare readOnlyHint=true, so safety is covered. The description usefully adds that response metadata includes totalByStageId and names the underlying endpoint (GET /v1/deals), but says nothing about pagination behavior or rate limits, even though the schema hints at a `next` cursor.

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?

Three short sentences, front-loaded with the resource and fields, then filters, then response/endpoint detail. Nothing is redundant or padded.

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 partially compensates by naming the carried fields and the totalByStageId metadata, and it covers the filter dimensions. It is nearly complete for a list tool, missing only explicit return-shape or pagination guidance.

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 all 8 parameters documented, so the baseline is 3. The description's filter list (pipeline, user, person, status) maps to existing parameters but adds no syntax, format, or behavioral nuance beyond the schema.

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 identifies the resource (deals/transactions) and enumerates the fields it carries, so an agent can tell it is the deal-listing tool distinct from fub_create_deal, fub_update_deal and the person/pipeline listers. However, it never uses a listing verb itself, relying on the name and title to signal the action, and it does not explicitly contrast itself with 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?

It states the filtering axes ('filter by pipeline, user, person or status'), which implies usage context, but offers no when-to-use versus alternatives (e.g., fub_list_pipelines to resolve IDs) and no exclusions or prerequisites.

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