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

Annotations already declare destructiveHint=true/openWorldHint=true, but the description adds real behavioral context beyond them: the server injects auth, signature, market, and correlation headers, and large bodies are truncated to a preview with the full payload available via the returned cached_at resource. That truncation and header-handling disclosure is genuinely useful and not present in the structured metadata.

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?

Purpose is front-loaded in the first clause, and each subsequent sentence carries distinct information (identification modes, header injection, body truncation). It is dense but earns its length; no filler sentences.

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 12-parameter tool with an output schema, the description covers the critical behaviors an agent needs: how to identify the endpoint, that auth is handled server-side, and how oversized bodies are returned. Return values themselves need not be explained given the output schema, though it could say more about the relationship to sibling discovery tools.

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 100%, so the baseline is 3, and each parameter is already documented in the schema. The description still adds meaning on top — the operation_id vs method+path+api interaction and the fact that a raw path reaches endpoints absent from the bundled specs — which goes beyond restating the 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 gives a specific verb and resource — 'Execute an authenticated API request' — with the concrete identification modes (operation_id, or method + path with an api). This distinguishes it in practice from list_endpoints/describe_endpoint, though it never names a sibling explicitly, so it stops short of a 5.

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 explains the two ways to identify an endpoint and notes that a raw path reaches alpha/beta/unpublished endpoints, which is useful context. However, it never states when to prefer this tool over describe_endpoint or list_endpoints, nor any prerequisite workflow (e.g. resolve operation_id first), leaving usage implied rather than explicit.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds real behavioral context the annotations cannot: that the result carries the full transitive schema closure rather than a shallow operation record, which is the key trait an agent needs to trust it for request-body construction. It omits error/not-found behavior for an unresolvable operation_id.

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, zero filler, and the payload guarantee is front-loaded right after the purpose. Nothing repeats the name or the annotations.

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?

An output schema exists, so return structure need not be restated, and the description covers purpose, scope and the semantic completeness of the result. The remaining gap is routing guidance against list_endpoints and any failure mode for ambiguous or unknown operation_ids.

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 100%: the schema already explains the qualified vs bare operation_id form and the api fallback for disambiguation. The description adds nothing about either parameter, so the baseline 3 applies.

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?

"Describe one OpenAPI operation" states a specific verb and a tightly scoped resource, and the second sentence pins down exactly what the response includes (the operation plus every transitively reachable components.schemas entry). An agent can distinguish this from list_endpoints (enumerate many) and call_endpoint (invoke) without opening any schema.

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 phrase "so a request body can be built without the full spec" implies the workflow position (inspect before composing/calling), but the description never explicitly says when to use this versus list_endpoints or call_endpoint, nor when not to use it. Usage is inferable rather than stated.

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

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

Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) leave the mutation oddity unexplained, and the description resolves it by disclosing the actual behavior: bytes are written to dest_path when given, otherwise gunzipped and cached, with redirects followed automatically. It stops short of stating auth/permission requirements, which the schema carries instead.

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?

Three tight sentences, front-loaded with the verb and resource, then the input modes, then the output behavior. No filler; only minor loss for packing several clauses into the middle sentence.

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 13-parameter tool with an output schema (so return values need no explanation), the description covers the targeting modes and the write-vs-cache outcome adequately. The remaining gap is the absence of sibling routing against call_endpoint.

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 already 100%, so the baseline is 3, but the description adds real meaning by showing the three mutually exclusive targeting modes (url vs operation_id vs api+method+path) and giving concrete examples of the URLs that work. It does not add syntax detail for params/tenant/path_params beyond the 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?

States a specific verb and resource: 'Download a report, label, or snapshot', with the scope prefixed by '[Walmart]'. It is clear what the tool fetches, but it never distinguishes itself from the sibling call_endpoint, which likely also retrieves remote data.

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 explains the three input modes (full url, operation_id, or api with method and path) which implies usage, but gives no explicit when-to-use/when-not guidance and never names call_endpoint or any sibling as the alternative for a given case.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful workflow context (ids are reusable downstream) but says nothing about pagination behavior or result shape beyond what the schema/output schema provide, so it adds only modest value over structured data.

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, front-loaded with the resource and scope, followed immediately by the actionable handoff. Zero filler.

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?

With an output schema, full annotation coverage, and 100%-documented parameters, the description only needs to establish purpose and workflow, which it does. A mention of pagination or that filtering is available would make it fully self-sufficient, but nothing critical is 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 100% and every parameter (api, tag, limit, offset, query, method, platform) is documented in the schema itself, including the platform-vs-api distinction and offset chaining. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('List OpenAPI operations') plus default scope ('across every api'). It names the downstream siblings describe_endpoint and call_endpoint, which helps situate it, though it doesn't contrast against them as alternatives (e.g. vs. refresh_specs or download_file).

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?

Clearly signals the discovery-first workflow: returned operation ids 'can be passed straight to describe_endpoint or call_endpoint.' That gives an agent a concrete reason to call this before those tools, but there are no explicit exclusions or when-not-to-use conditions.

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

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuinely useful context beyond the annotations: the refreshed specs land in a user cache that takes precedence over bundled copies, and the 'all 33' scope signals the blast radius of an unscoped call.

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, front-loaded with the action and destination, followed immediately by the one operational detail an agent needs (the default scope). No filler.

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?

Output schema exists so return values need not be explained, and the mutation's safety profile is covered by annotations. The description covers cache precedence and default scope well; it could have said where specs are sourced from (network) to justify the openWorldHint, but nothing critical to correct invocation is 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 coverage is 100% and the single param is optional, so the schema already carries the format example. The description's 'Omit api to refresh all 33' adds the default's practical effect (full refresh of 33 specs) which the schema's default=null does not convey.

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?

States a specific verb and resource ('Refresh OpenAPI specs') plus the destination ('user cache'), which is unambiguous. Sibling tools (list_endpoints, call_endpoint, download_file) serve unrelated functions, so no explicit differentiation is needed, but the description never contrasts itself with them or explains the bundled-vs-cache relationship scope beyond precedence.

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 phrase 'Omit api to refresh all 33' gives a clear default behavior, but there is no explicit guidance on when to use this tool versus, say, just reading bundled specs, nor any prerequisite or caution about when refreshing is unnecessary. Usage is implied rather than stated.

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