connectif_workflows

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

No annotations are present, so the description carries full responsibility. It discloses no side effects, authentication needs, or operational details. The tool merely says it performs 'direct API operations,' which gives no behavioral insight.

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 brief at two sentences, with no redundant filler. However, brevity is achieved at the expense of substance; it's under-specified rather than efficiently informative.

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 no parameters, the description leaves the agent without enough information to know what operations are available, what inputs are expected, or what results to expect. It fails to enable correct 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?

The input schema has zero parameters, but the description references an 'action' selector, implying an undocumented parameter. This confusingly contradicts the schema's empty parameter list, adding confusion rather than clarifying semantics.

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 identifies this as a tool for 'Connectif API operations for workflows,' conveying a resource area (workflows) but no specific verb or operation type. It distinguishes itself from sibling tools by the 'workflows' scope, but remains vague about what the tool actually does.

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?

No guidance is provided on when to prefer this tool over sibling tools. The phrase 'Use action to select an official operation' suggests an invocation detail but does not frame it as a decision between alternatives.

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