rest_call

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

The annotations only say readOnly=false, openWorld=true, destructive=false, so the description carries the real burden and does well: it discloses that {{variables}} are interpolated in path/query/headers/body, that extract writes values into session variables (a side effect beyond annotations), and what the response contains (status, parsed body, elapsed_ms). It omits error/failure behavior, whether redirects or retries occur, and what happens when a variable is undefined.

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?

Five dense lines, front-loaded with the core action, then parameter semantics, then return shape; nothing is padding. Minor cost: the shorthand 'x = y' formatting and the trailing return-shape sentence (redundant with the output schema) reduce scannability slightly.

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 10-parameter, 0%-coverage, open-world HTTP tool, the description covers the tricky parts (templating, extract, body vs body_text) but leaves environment, include_headers, and method/service usage unexplained, and gives no routing guidance against soap_call or the describe_* discovery tools. Adequate but with clear gaps.

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 0% (only bare titles), so the description must compensate, and it explains path, body vs body_text, extract's JSONPath map, and templating in query/headers with a concrete Authorization example. However, four parameters are never addressed: service, method, environment (which environment's base_url and credentials — a meaningful behavior), and include_headers.

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 opens with a clear verb+resource ('Call a REST endpoint') and clarifies that the path is relative to a named service's base_url, which distinguishes it implicitly from soap_call. It never explicitly names siblings like describe_operation or list_services, so an agent must infer the REST-vs-SOAP and discover-then-call split.

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?

Usage is only implied: the base_url/service relationship and the extract-to-session-variable mechanism hint at a multi-step workflow (describe_service -> rest_call -> reuse variables). There is no explicit when-to-use vs soap_call, no warning about calling before describe_operation, and no guidance on which HTTP methods are safe.

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