finance_stripe_revenue_audit

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

With no annotations, the description carries full burden but fails to disclose behavioral traits. It does not state whether the action is read-only, modifies data, or requires specific permissions. The scope info (JWT, tenant, company) is present but insufficient for 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 concise (3 sentences plus args) but under-specified. Every sentence is relevant, but the conciseness sacrifices completeness. Structure is logical: action, routing, arguments.

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?

Despite having an output schema, the description does not explain return values or the tool's domain-specific role. It provides no context about what a revenue audit entails or how inputs shape the output. Incomplete for an AI agent to use effectively.

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 description coverage is 0%, so the description must explain parameters. It describes 'message' as free-text objective and 'inputs' as optional JSON string, adding meaning beyond the schema's defaults and titles. However, it lacks specificity about valid input formats or examples.

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 merely restates the tool name as an action to run ('Run the finance domain agent action') and explains routing, but does not specify what the audit entails or distinguish it from sibling tools like stripe_account_health or finance_revenue_leakage. The purpose is vague.

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. The description only explains the routing mechanism, not the appropriate context or exclusion conditions.

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