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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds non-obvious behavior: the public feed is always active and only ever holds active listings, while drafts/closed deals surface only under scope 'mine', and the feed relevance-ranks a query. It does not cover pagination behavior or result caps, but that is minor against the annotation coverage.

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?

Front-loaded with the trigger, then scope semantics, then filtering, then the return-row composition, then the sibling hand-off. Each sentence carries information, though the scope explanation is repeated between the description and the schema's 'scope'/'status' fields.

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 compensates by enumerating what each returned row carries (title, summary, category, region, capital sought, status, link), and it explains defaults and scope-dependent visibility. Only pagination/limit behavior and the 'fields'/'detail' projection interaction are left to the schema.

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% and every parameter (scope, detail, fields, status, limit, offset, region, category, query) is already documented inline, including the status/scope interaction. The description largely restates those semantics, adding only the relevance-ranking note and the scope default. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource (browse deals / the member's own listings) and names the distinct retrieval modes ('feed' vs 'mine'). It also names the sibling it is not ('To post a new deal, use connections_deal_create'), so an agent can separate it from connections_deal_create without opening either schema.

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?

Opens with an explicit trigger list ('when the member asks about Deal Flow, deals, listings, what is for sale, raises, or their own postings') and hand-offs to the sibling that handles the excluded case (creating a deal). Both the when-to-use and the when-not-to-use condition are stated.

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