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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and scope are covered structurally. The description adds only the HTTP surface ('GET /deals') and the fact that results are filterable; it says nothing about result caps, pagination flow, or rate limits beyond what the schema already encodes.

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 sentences: the first front-loads what is returned and how it can be filtered, the second gives the endpoint. No filler, no redundancy, and the most important information (verb + resource + filter surface) comes first.

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 10-parameter, no-required-parameter list tool with annotations and no output schema, the description covers what the resource is and which dimensions can be filtered. It partially compensates for the missing output schema by naming the returned fields, but does not describe the paginated response envelope (limit/offset/next_offset) that the schema only hints at.

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 one of the 10 parameters is already documented in the schema, including pagination semantics ('Pass the previous reply's next_offset') and the stage_id cross-reference. The description merely mirrors a subset of the filter fields and omits limit, offset and include_custom_fields, adding no new meaning.

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 gives a specific verb ('List or search') and resource ('deals (sales opportunities)') plus the fields carried in results and the filterable attributes. It implicitly separates itself from teamgate_get_deal (single deal) and teamgate_list_contact_deals, but it never names those siblings, so an agent still has to infer the boundary.

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: the enumeration of filter dimensions (name, status, stage, owner, source, creation date) suggests this is the filtered collection endpoint, but there is no explicit when-to-use, when-not-to-use, or named alternative such as teamgate_search or teamgate_get_deal. Adequate but leaves routing to inference.

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