connectif_exports

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects, permissions, rate limits, data scope, or any operational consequences. 'Direct API operations' is too broad to be informative, and the reference to 'action' without schema validation is misleading.

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 short, but brevity is not conciseness when it sacrifices all substance. The first sentence is essentially a restatement of the tool name, and the second sentence is an unhelpful directive. It is under-specified rather than appropriately sized.

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 there is no output schema, no annotations, and an empty input schema, the description needed to provide operational context. It fails to explain what export operations are available, how 'action' maps to them, or what the tool returns. It is completely inadequate for an agent to use the tool correctly.

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 schema has zero parameters, yet the description instructs the agent to 'Use action to select an official operation,' implying a parameter that does not exist in the input schema. This contradiction creates confusion rather than adding meaning. The description does not compensate for the empty schema; it introduces an undocumented phantom parameter.

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 says 'operations for exports,' which is vague and lacks a specific verb or resource scope. It does not clearly differentiate from the many sibling Connectif tools, and 'use action' is a generic placeholder rather than a concrete capability.

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 only guidance is 'Use action to select an official operation,' which hints at a selection mechanism but provides no context for when to use this tool versus siblings, no prerequisites, and no exclusions. The absence of schema support for 'action' further weakens the guidance.

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