connectif_imports

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

No annotations are provided, so the burden is entirely on the description. The text does not disclose side effects, permission requirements, rate limits, return format, or any operational details. The agent is left completely in the dark about what execution entails.

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 text is extremely short, but brevity here is under-specification, not efficiency. Every sentence is vague and adds no actionable information, so the 'conciseness' is not a positive trait.

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 no annotations, no output schema, and an empty input schema, the description is expected to carry all contextual information. It fails to explain what the tool does, when to use it, or what to expect, making it completely inadequate for agent decision-making.

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 is empty, so the description must compensate, but it instead references an 'action' parameter that is absent from the schema. This is misleading and provides no meaningful semantic information about parameters or 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 'Direct Connectif API operations for imports' provides no specific verb or resource, and the instruction to 'Use action to select an official operation' references a parameter that does not exist in the schema. It fails to distinguish the tool from its siblings since it does not state what concrete task it performs.

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 alternatives. The description does not mention any context, prerequisites, or exclusions, making it impossible for an agent to decide when to invoke it.

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