CPI Invoke Function Import (run any operation)

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

With no annotations provided, the description carries the full burden. It discloses auto-quoting of string parameters, the need for ALLOW_WRITE permission, and the typical mutability of function imports. This goes beyond the schema, though it could mention idempotency or error behavior.

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 sentences, front-loading the purpose and quickly adding critical behavioral notes. Every sentence is necessary and no word is wasted.

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 the complexity (no output schema, 4 parameters, large sibling set), the description covers the essential aspects: what it does, how to use parameters, permissions, and side effects. Missing details about return values or error scenarios, but overall adequate for an invocation tool with a referenced catalog.

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?

Schema coverage is low (25%), with only 'confirm' having a description. The description adds value by noting that string parameters are auto-quoted, which informs the agent about parameter handling. However, it does not explain 'functionName' or 'method' beyond what the schema provides, leaving some parameters underdescribed.

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 clearly states the tool invokes any OData function import, specifying the resource (function imports) and the action (invoke). It references the sibling tool 'cpi_api_catalog' for discovery, distinguishing it from other tools that perform specific operations.

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?

The description provides context about permission requirements (ALLOW_WRITE) and side effects (most change tenant state), but does not explicitly state when to use this tool vs alternatives. It implies usage via the reference to cpi_api_catalog, but lacks explicit when-not or alternative guidance.

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