finance_autonomous_finance_loop

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds that execution is scoped to the JWT, tenant, and company and routed through a dispatcher, which is useful context. However, it does not disclose what side effects or autonomous decisions may occur.

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, stating the operation and routing in the first two sentences, then listing parameters. There is no filler or repetition of schema defaults.

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 destructive, non-idempotent, autonomous finance operation, the description is under-specified: it lacks warnings about consequences, expected outcomes, or when this loop should be launched. The output schema covers return values, but the absence of usage context and impact disclosure leaves an agent to invoke a potentially consequential action without understanding it.

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 carries the burden. It defines both parameters: `message` as a free-text objective and `inputs` as an optional JSON string of structured inputs. This is adequate for basic invocation, though it could say more about expected input shape.

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 a specific verb ('Run') and names the exact resource (`autonomous_finance_loop`), and clarifies it is routed through a domain-agent dispatcher. However, it never explains what the finance autonomous loop actually does, making it difficult to distinguish from many other `finance_*_loop` sibling tools.

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?

There is no guidance on when this tool should be used versus alternatives like `finance_chat`, `finance_query_data`, or other finance loop tools. The description explains the routing mechanism but not the conditions, prerequisites, or exclusions for using it.

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