connectif_products

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. The description gives no indication of side effects, mutability, required permissions, or whether operations are read-only. 'Operations' could include destructive actions, but this is not disclosed, leaving the agent without essential safety information.

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 only two sentences, which is concise, but it is under-specified rather than efficiently informative. It omits critical details and leaves the agent guessing about the tool's usage, making the brevity a drawback rather than a strength.

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 an empty input schema, no output schema, no annotations, and a vague description, the tool is critically under-documented. The description fails to explain what 'official operations' are available, what inputs are expected, what outputs are produced, or any constraints. This is completely inadequate for a tool that appears to be a multi-operation dispatcher.

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 input schema lists zero properties, yet the description explicitly instructs to 'Use action to select an official operation.' This introduces a parameter that is not defined in the schema, which is misleading and breaks the contract between description and schema. The agent cannot know what values 'action' accepts or how to provide it.

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 'Direct Connectif API operations for products' which identifies the resource but is vague about the specific operations. 'Use action to select an official operation' implies a generic dispatcher, but without listing operations it fails to clearly distinguish from sibling tools like connectif_contacts or connectif_purchases.

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?

There is no explicit guidance on when to use this tool versus alternatives. The only instruction is 'Use action to select an official operation,' which is a mechanism hint, not a usage guideline. It does not mention prerequisites, exclusions, or scenarios where sibling tools would be more appropriate.

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