connectif_store

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

With no annotations and this minimal description, the agent has no information about side effects, authorization requirements, rate limits, or response behavior. The phrase 'Direct operations' does not convey whether this is a read-only or mutating tool. This is a significant gap for a tool that may perform various operations.

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 at two sentences, but the second sentence is vague and does not earn its place. It is under-specified rather than effectively brief, providing too little detail to be useful.

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 absence of annotations, output schema, and defined parameters, the description is severely incomplete. It does not explain what operations exist, what the tool returns, or what 'store' specifically covers. The agent is left with no clear way to invoke or understand this tool among many siblings.

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 has zero parameters, yet the description says 'Use action to select an official operation', which implies an 'action' field that is not present in the schema. This inconsistency confuses rather than clarifies. The description adds no meaningful parameter semantics and even misleads about expected inputs.

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 it provides 'Direct Connectif API operations for store', which identifies the resource (store) and implies a set of operations. However, it does not enumerate which operations are available, and 'Use action to select an official operation' is vague. It only loosely distinguishes from sibling tools by resource type.

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 guidance on when to use this tool versus sibling tools like connectif_contacts or connectif_products. The only instruction is to use an 'action' parameter, which is not defined in the schema. No alternatives, exclusions, or prerequisites are mentioned.

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