connectif_contacts

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It does not state whether operations are read-only, mutating, require authentication, or have side effects. 'Direct API operations' is too generic to convey meaningful behavioral traits.

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 a single short sentence, which is concise. However, conciseness without substance is not beneficial—the content is nearly tautological and does not earn its place by adding useful information.

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 no output schema, no annotations, and an empty input schema, the description is utterly incomplete. It does not explain what operations are possible, how the action is specified, or what returns. The reference to an undocumented 'action' further compounds the incompleteness.

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 with 0 parameters, so there is nothing to document. However, the description misleadingly instructs to 'Use action to select an official operation,' implying a parameter that does not exist in the schema. This directly miscommunicates the tool's interface.

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 contacts' is vague—it identifies the resource (contacts) but provides no specific verb or operation. 'Use action to select an official operation' implies a selector but doesn't specify what operations are available. It fails to distinguish clearly from sibling tools beyond the contacts domain.

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 given on when to use this tool versus alternatives like connectif_purchases or connectif_contact_fields. The mention of 'action' suggests some selection mechanism but does not explain appropriate contexts, prerequisites, or exclusions.

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