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

No annotations are provided, so the description carries the full burden of disclosing behavior. It mentions using the buyer's saved connection details but does not disclose that this tool can execute arbitrary HTTP methods (including mutations), that non-GET requests require confirmation, or that dry-run mode exists. The potential for side effects is not surfaced at all.

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 a single concise sentence that is front-loaded with the tool's purpose. No filler or redundancy.

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 generic raw API tool with 7 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain how to construct a request, what to expect in the response, or what safety mechanisms exist. The rich schema partially compensates, but the description alone leaves significant 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?

The input schema already provides detailed descriptions for 86% of parameters, including path, method, confirm, dry_run, body_json, query_json, and headers_json. The description adds no additional parameter semantics, but given the high schema coverage the baseline of 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?

The description clearly identifies the tool as a generic API request tool for any documented endpoint in the Factorial ATS Ops Control Plane. This distinguishes it from the many specific sibling tools that target individual resources/operations. The verb 'use' is somewhat generic but combined with the resource description it is unambiguous.

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 this tool is for making requests to any documented endpoint, but it does not explicitly state when to prefer this over the dedicated sibling tools. There is no mention of fallback scenarios or exclusions. The 'documented' constraint offers some guidance but no explicit alternatives are named.

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