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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this is a list-returning read whose authorization and charges are handled by the caller's OpenAny gateway, but it does not explain pagination behavior, rate limits, or what a Connection record contains.

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 short sentences, front-loaded with the operation and followed by relevant gateway credential and billing context. There is no filler or redundant restatement.

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 six-parameter data-retrieval tool with no output schema and no annotations, the definition is only minimally complete. It does not characterize the returned connection records or pagination behavior, leaving the schema and title to carry much of the meaning.

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 coverage is 83%, and the schema already documents the domain/UUID input, category filter, date filters, page, and limit. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific read operation: it returns a list of a company's Connections, and the title clarifies those connections are partners, customers, and investors by domain. It does not explicitly distinguish this from sibling PredictLeads endpoints such as financing events or news events, so it stops short of 5.

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 says what is returned and mentions gateway credentials, but gives no when-to-use, when-not-to-use, or comparison with sibling company-data tools. An agent must infer from the title that this is the relationship-data endpoint rather than the news, financing, or technology endpoint.

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