finance_capital_allocation_loop

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

With no annotations, the description carries full burden but only says it routes through a dispatcher. No mention of side effects, return values, or whether it is a long-running or blocking process.

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 with the action name, followed by scope and args. It is concise but could be slightly tighter.

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?

The description lacks details about the tool's outcome, behavior, or tie to domain context. Even with an output schema, the agent cannot understand when or why to invoke this generic action wrapper.

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 coverage is 0%, and the description adds minimal meaning: 'Free-text objective' for message and 'Optional JSON string of structured inputs' for inputs. This is slightly better than the schema alone but still vague.

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 it runs a finance domain agent action 'capital_allocation_loop', but does not explain what this action does. It vaguely identifies the resource and verb but lacks specificity to distinguish from other finance tools like finance_capital_allocation_analysis.

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 on when to use this tool versus alternatives. The description only mentions scope (JWT, tenant, company) which is generic across many tools, not specific to this action.

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