jumpcloud_openapi_discovery

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 'Read-only' and 'Risk: low,' which are important behavioral traits. However, it does not describe the return format or pagination behavior, so it isn't fully transparent.

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 three terse sentences, front-loaded with the core purpose ('Read-only OpenAPI discovery'). Each sentence adds useful information—purpose, usage timing, and exclusion/risk—without any wasted words.

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?

For a simple read-only discovery tool, the description covers purpose and safety, but it omits any explanation of parameters (limit, domain) and does not hint at the response structure (no output schema). This leaves gaps for a complete understanding, though the tool's simplicity keeps it at a moderate level.

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 schema has no descriptions for the three parameters, and the description only implicitly covers 'search' via 'search operationId/method/path/tag metadata.' It gives no explanation of 'limit' or 'domain' semantics, so it fails to compensate for the 0% schema coverage.

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 'Read-only OpenAPI discovery' and specifies the exact resource and action: 'search operationId/method/path/tag metadata before invocation.' This distinguishes it from execution tools like jumpcloud_operation_invoke, which are present in the sibling list.

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 explicitly states when to use ('before invocation') and when not to ('Do not use as an execution tool'), providing a clear exclusion. However, it does not name specific alternative tools, so it falls short of a full 5 for 'explicit alternatives.'

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