stripe_raw_api_request

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

With no annotations, description carries full burden. It discloses important governance flow for non-GET requests (simulator, audit, idempotency, human-approval). However, it omits details on authentication, rate limits, error handling, or response behavior. Output schema may cover return values, but behavioral aspects are partially addressed.

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?

Description is concise with a brief overview followed by a bulleted argument list. No extraneous text. Purpose is front-loaded. Every sentence adds value.

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 presence of an output schema (not shown) and the tool's nature as a raw API proxy, description covers main behavioral aspects and parameters. However, it lacks details on GET request handling, error scenarios, and execution model nuances. Mostly complete but with minor 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%, so description compensates by explaining all 5 parameters with examples for api_path and base_address, and listing allowed methods. However, there is a discrepancy: params is described as 'JSON object' but schema defines it as a string. This could cause confusion. Overall, adds meaningful context beyond 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?

Description clearly states it is for 'governed long-tail Stripe API request for /v1 or /v2 endpoints', distinguishing it from sibling tools that cover specific Stripe operations. The verb 'request' with scope 'long-tail' and endpoint versioning provides a clear, specific 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 long-tail endpoints not covered by sibling tools, but no explicit when-to-use or when-not-to-use guidance. No mention of alternatives within Stripe family. Description notes behavioral differences for non-GET vs GET, but doesn't clarify when to prefer this over specific Stripe tools.

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