finance_tax_workflow

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 available. The description adds only auth scoping (JWT, tenant, company) but does not disclose what the workflow may create, modify, or destroy, or whether it is asynchronous. This does not contradict the annotations, but adds limited behavioral context beyond them.

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 organized with an Args list, with no fluff. The opening sentence is redundant with the tool name, but overall it is efficient and readable.

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?

This is a workflow runner for a domain-specific tax action, yet the description omits the core business behavior, expected inputs, output semantics, and selection criteria. With dozens of finance siblings, an agent cannot tell what objective to pass or when this tool is the right choice. The existence of an output schema does not fill the missing purpose and usage gap.

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. It provides one-line glosses for message ('Free-text objective') and inputs ('Optional JSON string of structured inputs'), but these largely repeat the schema property names and types. No examples, valid input keys, or guidance on how the two parameters interact are given.

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 opens with 'Run the finance domain agent action `finance_tax_workflow`', which merely restates the tool name. It adds routing details about the dispatcher and JWT/tenant/company scope but never explains what the tax workflow actually does, leaving the agent unable to distinguish it from the many other finance_* 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 to use this tool versus alternatives such as finance_query_data, finance_tax_obligation_scan, or the generic dispatch_domain_agent. The only contextual remark about routing through the domain-agent dispatcher is an implementation detail, not a usage criterion.

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