Load an OpenAPI/Swagger spec

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

No annotations are provided, so the description carries the burden. It does disclose key behavior: full dereferencing, JSON/YAML support, and that it returns title, servers, and every endpoint. However, it does not mention error handling, network dependency, or whether dereferencing can resolve remote references, leaving some behavioral uncertainty.

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 short sentences with no filler. The primary action and return value are front-loaded, and the usage instruction 'Call this first' is placed early. Every phrase earns its place.

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 single-parameter loading tool with no output schema, the description tells the agent what it returns and when to call it. It is reasonably complete, though error or dereferencing edge cases are not covered. Those gaps are minor for the agent's selection and invocation decision.

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 already provides complete coverage of the single 'source' parameter with a clear example. The description adds 'JSON or YAML' and 'fully dereference' context, but this is only marginal value beyond the schema. Baseline 3 is appropriate given high 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 states a specific verb and resource: 'Load and fully dereference an OpenAPI/Swagger spec from a URL or local file path.' It also clarifies what the tool returns, immediately distinguishing it from sibling tools like list_endpoints, call_endpoint, and test_endpoint. This makes it unambiguous as the initial loading step.

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?

'Call this first' explicitly signals prerequisite usage before other API tools. It does not enumerate when-not-to-use or name alternative loaders, but the sibling list makes the workflow context clear. This is strong practical guidance.

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