jumpcloud_operation_invoke

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

With no annotations, the description carries the transparency burden. It does disclose that mutating calls require an admin key and notes that risk is variable, which is helpful. However, it does not explain the arbitrary execution nature, potential side effects, error behavior, or return format, leaving significant behavioral ambiguity.

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 and front-loaded with the primary usage pattern. The phrase 'Risk: variable' is vague but not verbose; overall it is concise without significant waste.

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 is a complex generic invoker with no annotations, no output schema, and 9 parameters at 0% schema coverage. The description lacks essential context about how to discover operationIds, how body/query/headers interact, and how tenant/user/token context applies. It provides only minimal information, making it insufficient for a tool with this scope.

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 description coverage is 0%, so the description must compensate. It explains operationId and pathParams, and implies authorizationKey for mutating calls, but ignores body, query, headers, userId, tokenId, and tenantId. These parameters are likely essential for many operations, so the description only partially covers the 9-parameter schema.

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 identifies the tool as an 'OpenAPI operation invoker' and instructs to use operationId+pathParams, which conveys the core function of invoking a specific API operation. However, it does not explicitly distinguish this from the sibling jumpcloud_api_request tool, so it lacks overt sibling differentiation.

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 gives usage direction ('Use operationId+pathParams for high-fidelity execution') and a prerequisite ('Mutating calls require admin key if configured'). It does not explicitly state when to prefer this tool over alternatives like jumpcloud_api_request or jumpcloud_openapi_discovery, so context is implied rather than fully specified.

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