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

The description discloses the conditional inclusion of notes (once bound to a company), the maximum return count (10 of each), the output shape ({results: [{id, title, url}]}), and that each id can be used with fetch. This goes beyond the read-only annotation to explain actual 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?

The description is concise, with no filler. It front-loads the primary purpose, then provides return details and usage context in a logical order. Each sentence contributes distinct information, and the structure is easy to parse.

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?

Given the tool's simplicity (single parameter, no output schema), the description covers all essential aspects: the search scope, conditional notes, return limit, result format, round-trip capability, and the intended client environment. Nothing needed for correct usage is missing.

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?

The only parameter 'query' has a schema description of 'Plain-text search terms' and the tool description repeats exactly the same phrase. Since the description adds no additional meaning beyond the schema, the baseline score of 3 applies.

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 clearly states the action (search), the resource (Deal Flow marketplace deals and member notes), and the filtering condition. It also differentiates from other tools by indicating it targets clients that only speak search/fetch, making its purpose 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?

The description explicitly specifies when to use this tool: for clients limited to search/fetch interactions, and contrasts it with connections_pulse and connections_execute for full native tool access. This provides clear contextual guidance for selection.

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