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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real context: organization scoping, that it runs under normal user permissions, that calls are audit-logged, and that exports/large results come back as a bounded downloadable result. That result-shape and audit disclosure is exactly the kind of thing annotations cannot express; only error behavior for an invalid operationId is left out.

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, no filler, and the scoping/permission constraint is front-loaded before the result-shape caveat. Every clause carries information an agent would otherwise have to infer.

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 generic gateway with 0% parameter documentation, no output schema, and nested untyped objects, the description answers too few of the questions an agent must resolve before calling it: where the operationId comes from, what the query/params maps accept, and what happens on failure are all missing.

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% and all three parameters include nested free-form objects, so the description must carry the burden and it does not. Neither 'operationId' (a 24-hex id whose source is unstated), nor the opaque 'query' and 'params' objects (string-valued, 2000-char capped) is explained, leaving an agent to guess what goes into them.

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 verb+resource pairing ('Execute... GET operation') is real but abstract: an 'operation' is the gateway's own concept, and the description never says how operations are identified or that they are looked up elsewhere. It also fails to distinguish this generic executor from the many concrete get_* siblings that overlap with it.

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?

There is no when-to-use guidance at all: no mention of describe_operation or search_operations to obtain the required operationId, no statement of when to prefer this gateway over the dedicated get_* tools, and no indication of when read_download (the obvious alternative for bounded exports) should be used instead.

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