finance_investment_trader_orchestration_loop

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

Annotations already convey destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the agent knows this is a mutating, non-idempotent operation. The description adds context about JWT/tenant/company scoping and dispatcher routing, which is useful, but it does not describe what side effects occur or what the orchestration loop will do beyond 'run'.

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 well-structured: a clear first sentence, a routing/scoping sentence, and a terse args listing. There is minimal filler and the most important invocation detail appears first.

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 complex orchestration-loop tool with destructive annotations, no required parameters, and no sibling differentiation, the description is too thin. An agent has no way to know what objective to supply, what inputs the loop expects, what the output represents, or when this tool should be preferred over closely related investment trading tools.

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 is the only source of parameter meaning. It does add some value by defining `message` as 'Free-text objective' and `inputs` as 'Optional JSON string of structured inputs,' but it does not explain what structured inputs are expected, what keys are valid, or how they interact with the message.

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 identifies a clear action ('Run the finance domain agent action') and names the exact action being run, so an agent can tell this is an invocation entry point. However, it never explains what the `investment_trader_orchestration_loop` actually does, what objective it accomplishes, or how it differs from closely named finance siblings such as `finance_investment_trading_agent` and `finance_investment_trading_signal`.

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 given about when to call this tool versus other finance or orchestration tools. The description only mentions routing mechanics ('Routes through the platform's domain-agent dispatcher'), not use cases, prerequisites, or alternatives.

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