finance_revenue_leakage

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions routing through a dispatcher under JWT/tenant/company scope, but omits critical traits such as side effects, rate limits, data access, or output characteristics. Insufficient for an agent to assess behavior.

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 very concise (3 sentences) and front-loads the action name, routing info, and parameters. Every sentence serves a purpose, though the content is sparse.

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 (not described), the description is incomplete for a domain agent tool. It fails to explain the function's purpose, return value, or how it fits among many finance siblings, leaving significant gaps for an agent to understand its role.

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 description adds minimal meaning beyond the input schema by labeling 'message' as a free-text objective and 'inputs' as an optional JSON string. Given 0% schema description coverage, this provides basic utility, but it lacks detail on expected format or constraints.

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 states 'Run the finance domain agent action finance_revenue_leakage,' which is a tautology of the tool name. It does not explain what revenue leakage detection or analysis entails, nor does it distinguish from sibling finance tools like finance_aging or finance_anomaly_fraud_case_file.

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 compared to alternatives. The description lacks context on scenarios, prerequisites, or exclusions, leaving the agent to guess when to invoke it over other finance tools.

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