Get cataloged 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 an important trait: the operation is not invoked, indicating a read-only, side-effect-free behavior. However, it does not mention error behavior (e.g., what happens on no match) or return format details, so transparency is partial. The explicit 'does not invoke' is valuable but not comprehensive.

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 deliver the core purpose, a constraint, and a crucial non-invocation note — no filler. The main action is front-loaded, and every clause earns its place. It is efficiently structured for quick comprehension.

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?

As a retrieval tool with no output schema, the description should at least indicate what structure the 'operation' takes or what happens when no match is found. It says it 'returns one operation' but does not describe the return object or error cases. Given the sibling tools and the absence of an output schema, the description is under-specified for an agent to know exactly what to expect or how to handle failures.

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 only 33% (only 'path' has a description). The description adds meaning for 'method' and 'path' by stating they must match the published spec exactly, but it never explains 'apiId' — what it represents or how to obtain it. Thus, two of three parameters get some semantics, but the most opaque one remains undocumented, and the tool text does not fully compensate for the low 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 clear action ('Return one operation') and resource ('from a cataloged API'), and distinguishes itself by explicitly noting it 'describes the operation; it does not invoke it.' This sets it apart from tools that might execute API calls and makes its purpose unambiguous.

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 conveys a prerequisite ('Method and path must match the published spec exactly') and a key differentiator ('does not invoke it'), but it does not explicitly compare with sibling tools like list_catalog or inspect_contract. The context of when to choose this over alternatives is implied rather than stated, so some guidance exists but lacks explicit routing.

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