connectif_custom_integrations

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

No annotations are provided, so the description must disclose behavior on its own. It only hints at 'direct' API operations and an 'action' selector, but doesn't mention side effects, permissions, rate limits, or return values.

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?

Two sentences, short and to the point. However, it's under-specified; the 'action' parameter is mentioned but not explained, so brevity comes at the cost of completeness.

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 zero parameters, no annotations, and no output schema, the description is the only source of context. It fails to explain what operations are available, how the 'action' parameter works, or what the tool returns, leaving the agent without essential guidance.

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 baseline is 4, but the description introduces an 'action' parameter that isn't in the schema. It adds some meaning (action selects operation) but doesn't explain value formats or options, so it falls short of the baseline.

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 names the resource 'custom_integrations' but uses the vague verb 'operations' without specifying a concrete action. It distinguishes from siblings by resource name but lacks a clear 'what it does' statement.

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?

It mentions 'Use action to select an official operation' but provides no guidance on when to use this tool versus the many sibling connectif_* tools. No context, prerequisites, or exclusions are given.

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