stripe_create_refund

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects (e.g., does it immediately refund?), idempotency, error conditions, or permission requirements. It only describes the route, which is not behavioral context.

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 short but includes extraneous routing details (JWT, tenant, company scope) that are not essential for selecting or invoking the tool. The structure is straightforward but could be better organized with a clear action statement first.

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 this is a mutation tool with no annotations and minimal description, the definition is incomplete. An agent needs external knowledge about Stripe refunds to use it correctly. Prerequisites, return format (though output schema exists), and error states are not mentioned.

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 schema has 1 parameter 'arguments' (string) with no description. The description adds that it is a 'JSON string of arguments for the connector operation' but does not specify expected fields (e.g., charge, amount). With 0% schema coverage, the description fails to compensate.

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 states it is a 'Stripe connector operation create_refund' but does not explicitly state the action (e.g., 'Creates a refund for a Stripe charge'). The name implies the purpose, but the description lacks a specific verb+resource statement.

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?

No guidance is provided on when to use this tool, what prerequisites are needed (e.g., a charge ID), or how it differs from alternatives like square_create_refund. The description only contains routing and authentication details.

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