mcp_api_client

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

The description discloses key behaviors: auth_token is prefixed into Authorization header unless overridden, local URLs are allowed, and responses are structured results or MCP errors. However, it lacks disclosures about potential risks (e.g., local URL access), rate limits, or idempotency of actions.

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 very concise: two sentences that front-load the purpose ('HTTP caller') and efficiently explain all parameters and behaviors without unnecessary words.

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?

The description covers all parameters and key behaviors, and mentions response format ('structured results or MCP errors'). However, without an output schema, more detail on response structure would improve completeness.

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?

With 0% schema description coverage, the description fully compensates by explaining all five parameters: action enum, url requirement, data for mutating verbs, headers as string map, and auth_token behavior. This adds significant meaning beyond the bare 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 clearly states it is an HTTP caller, lists all six supported actions (get, post, put, delete, patch, check_api), and specifies that it makes HTTP requests. It is distinct from sibling tools (database and SSH managers) by focusing on HTTP calls.

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 implies usage for making HTTP requests by explicitly detailing action verbs and parameters. However, it does not provide explicit when-to-use or when-not-to-use guidance, though the sibling tools are sufficiently different that confusion is unlikely.

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