finance_domain_artifact_handoff

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

No annotations exist, and the description only states that routing occurs under JWT/tenant/company scope. It does not disclose side effects, destructiveness, permissions, or what the handoff entails.

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 but includes a redundant first line that repeats the tool name. It is structured with a brief docstring-like format, but is not ideally concise.

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?

Given the complexity (many siblings, no annotations, optional parameters, existing output schema), the description is incomplete. It does not explain what the tool returns, when it should be used, or provide enough detail for correct invocation.

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 briefly explains parameters: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs'. This adds some meaning beyond the empty schema descriptions, but remains vague and does not specify expected formats 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 repeats the tool name ('Run the finance domain agent action ...') and vaguely mentions routing through a dispatcher, but does not define what a 'domain artifact handoff' is or what it accomplishes. It fails to distinguish from sibling tools like it_ops_domain_artifact_handoff.

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 other finance domain tools or sibling artifact handoffs. Prerequisites, context, and alternatives are not mentioned.

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