finance_domain_artifact_handoff

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

Annotations already convey destructiveHint=true, so the description does not need to restate that, but it would ideally explain what side effects or destruction may occur. The description does add useful context about JWT, tenant, and company scoping and the dispatcher routing, which goes beyond the structured metadata. Still, the actual behavior of 'handoff' remains opaque, especially given the destructive annotation.

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 includes an Args section, which is easy to scan. The opening sentence largely restates the tool name and adds limited value. Overall it is acceptable but not especially rich or well-front-loaded.

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 tool with a destructive annotation and a generic 'handoff' action, the description does not provide enough context for an agent to know what the action does, when to invoke it, what inputs to supply meaningfully, or what consequences to expect. The output schema exists but is not described; the routing and scope details are the only substantive context. This is insufficient for reliable selection and invocation among the large sibling list.

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 must compensate, and it does partially by explaining message as a free-text objective and inputs as an optional JSON string of structured inputs. This adds meaning beyond the plain string types in the schema. However, it does not describe what structure inputs should take, what objectives are expected, or what the action consumes, leaving significant ambiguity.

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 the tool as running the finance domain agent action `domain_artifact_handoff` and clarifies that it routes through the domain-agent dispatcher. However, it never explains what the handoff action actually does, so the agent cannot tell from the description whether this is the right tool for a task. It is distinguishable mainly by the 'finance' prefix rather than by a clear functional outcome.

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 to use this tool versus alternatives such as dispatch_domain_agent, it_ops_domain_artifact_handoff, or finance_chat. The routing/scoping sentence is a mechanical detail, not a usage condition. The agent is left to infer when a handoff is appropriate.

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