stripe_create_invoice

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only implies a mutation ('create') but does not state side effects, required permissions, rate limits, or what happens if creation fails. This is a significant gap for a mutation tool.

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 and front-loaded with the purpose. It includes routing information, which may be extraneous but does not severely hinder clarity. Every sentence contributes, though some brevity sacrifices completeness.

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 simple create tool with one parameter and an existing output schema, the description is incomplete. It omits behavioral details, usage guidelines, and internal parameter expectations. The agent would need significant external knowledge or trial-and-error to use the tool correctly.

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 single parameter 'arguments' is described as a JSON string for the connector operation, adding minimal meaning beyond the schema. However, the description does not specify the expected internal structure or keys required for the underlying Stripe operation, leaving the agent undersupported.

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 to create an invoice, but it merely restates the name without elaborating on what creating an invoice entails. It is a minimal clarification, not a tautology, but lacks specificity.

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 versus alternatives like stripe_create_refund or stripe_list_invoices. There is no mention of prerequisites, preconditions, or scenarios where this tool should be avoided.

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