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

readOnlyHint=true already establishes this as a safe read. The description adds two things beyond the annotations: the return metadata field totalByStageId and the upstream endpoint GET /v1/deals. It says nothing about pagination behavior (the `next` token the schema alludes to) or response shape otherwise, so the added value is modest.

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 compact sentences with the resource and its fields front-loaded, then filters, then return note and endpoint. No filler, though the telegraphic fragment style is terse rather than richly structured.

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 does step in to mention totalByStageId in the response metadata, and the filter surface is covered by the schema. Minor gaps remain around paging (the schema hints at `next` but the description never explains it) and default page size.

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 every parameter (limit, offset, status, userId, personId, pipelineId, includeDeleted, includeArchived) is already documented. The description's filter list (pipeline, user, person, status) merely paraphrases a subset of them and adds no syntax or format detail.

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+resource ('Deals (transactions)') and enumerates the payload it returns (stage, price, people, agents, commission) plus its filter axes. It does not name or contrast itself against siblings like fub_search_people or fub_get_person, so it is clear but undifferentiated.

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?

'Filter by pipeline, user, person or status' implies when the tool is useful, but there is no explicit when-to-use/when-not guidance and no mention of alternatives (e.g., fetching a single deal or a person's deals). Usage is inferred rather than prescribed.

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