grc_tax_compliance_report

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description does not need to repeat those signals. It adds some useful context about routing through the domain-agent dispatcher under JWT, tenant, and company scope, which conveys auth and execution behavior. However, it does not describe what side effects may occur or what the action actually changes.

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 the core action stated first and parameter definitions in a clear bulletized section. Every sentence adds some information about invocation or scoping, with no fluff.

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 tool's optional parameters and existing output schema, the description adequately supports a basic call. However, it omits what a tax compliance report actually does, what outputs to expect, and when to choose this specific action over related grc or legal tax tools, making the tool harder to select confidently.

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 carries the burden for parameter meaning. It provides basic semantics for both parameters: message is a free-text objective, and inputs is an optional JSON string of structured inputs. This is enough to invoke the tool correctly, though not enough to know what structured inputs are expected.

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 a specific verb and resource: 'Run the grc domain agent action tax_compliance_report.' This is clear at the surface level and identifies the action being invoked, but it does not differentiate this tool from closely related siblings such as grc_tax_obligation_scan or legal_tax_compliance_report.

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?

The description provides no guidance on when to use this tool versus alternatives. It explains the routing mechanism and scoping but does not state the intended scenario, prerequisites, or when a different tax-related or grc tool would be more appropriate.

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