run_api

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

Discloses that errors from the tested API are not tool errors, a key behavioral trait. No annotations provided, so description carries full burden; could add more details like auth requirements or rate limits.

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, front-loaded with purpose, no 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?

Returns status/headers/body but not format details. No output schema to compensate. Could explain structure or error handling more thoroughly.

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?

Description does not elaborate on parameters beyond what schema provides. With 60% schema coverage, description should add value but doesn't explain method, body, or 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?

Description clearly states it runs tests by sending requests to real paths and returns status/headers/body. It distinguishes from sibling tools like create_api or get_api by specifying its testing purpose.

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?

Implied usage for testing APIs, but no explicit guidance on when not to use it or alternatives among sibling tools like get_api for definitions.

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