legal_tax_compliance_report

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

The description adds useful context beyond the annotations: it reveals that execution routes through a domain-agent dispatcher and is scoped by JWT, tenant, and company. This gives the agent meaningful expectations about authorization and indirection, while `destructiveHint` and `readOnlyHint` already cover the mutation profile.

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 compact and front-loaded, with a clear command first, execution context second, and argument semantics last. It avoids fluff, though it is so terse that some important selection context is left out.

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?

Despite having annotations and an output schema, the description is not complete enough for an agent to confidently invoke the tool. It omits what tax compliance reporting actually does, what valid inputs look like, and how it differs from close siblings like `grc_tax_compliance_report`.

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 partially compensates by explaining `message` as a free-text objective and `inputs` as an optional JSON string. This is helpful but the `inputs` field remains underspecified—an agent cannot tell what structured inputs the action expects.

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 says it runs the `tax_compliance_report` legal-domain agent action, which is a clear verb-plus-resource statement. It does not, however, distinguish this tool from closely related siblings like `grc_tax_compliance_report` or `legal_tax_obligation_scan`, and it never explains what the underlying action actually produces.

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 when-to-use or when-not-to-use guidance is provided. The routing and scoping details explain how the action executes, but an agent gets no help choosing between this tool and the many related legal/GRC/tax sibling tools.

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