finance_stripe_orchestrator

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

The description only mentions routing through a dispatcher; it discloses no behavioral traits such as whether the tool is read-only, destructive, requires permissions, or has rate limits. Annotations are absent, so the description fails wholly to provide transparency.

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 has a clear structure (title, routing, args). However, conciseness is only beneficial when the content is informative; here, the brevity comes at the cost of completeness. It is not excessively long but lacks necessary details.

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 tool's implied complexity as an orchestrator and the richness of sibling tools, the description is severely incomplete. It does not explain what tasks the orchestrator can perform, the expected input/output, or how it relates to specific Stripe actions. The presence of an output schema is ignored.

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?

With 0% schema description coverage, the description must add meaning. It labels 'message' as a free-text objective and 'inputs' as optional structured inputs, but it does not clarify valid objectives, input format constraints, or examples. The added value is minimal.

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 starts with 'Run the finance domain agent action finance_stripe_orchestrator', which is tautological. It adds routing context via the dispatcher but fails to state what the orchestrator actually does, leaving its purpose vague. It does not distinguish itself from numerous sibling tools like finance_stripe_dunning_recovery or stripe_create_invoice.

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 orchestrator versus the many specific Stripe actions (e.g., stripe_list_invoices, stripe_raw_api_request) or other finance tools. There are no explicit when-to-use or when-not-to-use instructions.

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