general_api_request

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

No annotations are present, so the description carries full burden. It mentions HTTP methods but does not disclose potential side effects, error handling, response format, or auth requirements, leaving gaps for a general request tool.

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?

The description is efficiently structured with a one-line summary followed by a bulleted list of arguments. No unnecessary words, and it is easy to scan.

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?

Given the tool's flexibility and absence of output schema/annotations, the description covers purpose, usage, and parameters adequately. Missing details on output and error behavior, but reasonable for a general tool.

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%, but the description provides clear explanations for each parameter (method, path, params, body, cluster), adding meaning beyond the bare schema. Slightly more detail on formats would improve it.

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 clearly states it performs a general HTTP API request for Elasticsearch/OpenSearch APIs, and explicitly distinguishes from siblings by noting it is for APIs without a dedicated tool.

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?

Provides explicit guidance: 'Use this tool for any Elasticsearch/OpenSearch API that does not have a dedicated tool,' effectively telling the agent when to use it versus the sibling tools.

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