list_contact_connections

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

No annotations are provided, so the description must convey behavioral traits. It states 'List all contact connections' implying a read operation, but does not disclose pagination behavior (via top parameter), default limits, or any other side effects. The description lacks depth on what the tool actually does.

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 very short (two sentences) and front-loaded with the action. However, it sacrifices necessary details, making it somewhat under-specified rather than concise.

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 that an output schema exists, return values are covered, but the description still lacks completeness for parameter usage and differentiation from sibling tools. The tool's complexity is moderate, but the description does not adequately guide selection or invocation.

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 0%, so the description must explain parameters. It mentions filter_expr for OData filtering, which adds meaning. However, the top parameter is not explained at all (likely for pagination), and the default values are not clarified.

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 verb 'list' and resource 'contact connections', indicating the action and subject. However, it does not differentiate from sibling tools like list_contact_connections_for_client or list_contact_connections_for_contact, which are more specific.

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 mentions using filter_expr for OData filtering, giving some usage context. But it does not specify when to use this general list versus the filtered variants, nor does it provide exclusion criteria.

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