connectif_coupon_sets

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

With no annotations provided, the description must disclose behavioral traits, but it only states 'Direct Connectif API operations' without addressing safety, side effects, permissions, rate limits, or return behavior. The phrase 'Use action to select an official operation' does not reveal what the tool actually does or its consequences, leaving the agent completely uninformed about potential mutations or read-only nature.

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 two short sentences with no fluff. It is front-loaded with the resource name and provides a brief usage hint. While under-specified, the structure is concise and would score higher if the content were more 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?

This tool has an empty schema, no output schema, and no annotations, so the description is the sole source of information. It fails to explain what operations are available, how the 'action' selector works, or what the tool returns. Sibling tools cover many other resources, and an agent cannot select or invoke this tool correctly without additional context. This is completely inadequate for a functional tool.

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 (100% coverage trivially), so per the rubric the baseline is 4. The description mentions 'action' but does not define it as a schema parameter, which is a minor inconsistency. However, since there are no parameters to document, the description does not need to add further parameter meaning, though the 'action' reference is unexplained.

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 coupon_sets' essentially restates the tool's name and resource without a specific verb or action (e.g., list, create, update). 'Use action to select an official operation' hints at a generic proxy but does not clarify what operations are available, making the purpose vague and nearly tautological.

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 use this tool versus sibling tools like connectif_contacts or connectif_products. The instruction 'Use action to select an official operation' is an internal usage step, not a contextual recommendation. There is no mention of alternatives, exclusions, or prerequisites.

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