Assess Regulatory & Demographic Bias

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, and nothing in the description contradicts them. The description adds which legal standards are being checked, which is useful context, but leaves unexplained behavior untouched — notably why the call is non-idempotent (presumably LLM-judgment variability) and how results are delivered.

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?

A single front-loaded sentence with no filler, and the legal frameworks are listed immediately after the verb. The dense acronym cluster (EEOC/SIOP/ECOA) is slightly hard to parse but is backed by the schema enum, so the compression costs little.

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?

There is no output schema, so the description should say what an assessment produces (a verdict, a score, cited violations, remediation guidance) — it says nothing about return shape. For a two-parameter, read-only tool that is otherwise well covered by annotations and schema, this is a real but bounded 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 100%, with both `systemPrompt` (including the 8,000-character cap) and the `complianceDomain` enum fully documented in the schema itself. The description's parenthetical abbreviations do little more than restate the enum values already present in the schema, so the baseline 3 applies.

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 (verifies compliance) and a precise resource (fair-lending, fair-housing, EEOC/SIOP/ECOA employment, and COPPA child-safety standards), and those categories map cleanly onto the `complianceDomain` enum values. An agent can tell this is a regulatory-bias assessment rather than a general audit or trace analysis. It stops short of explicitly contrasting itself with the many sibling audit/evaluate 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?

Usage is implied by the enumerated compliance frameworks — you reach for this when you need an EEOC, ECOA, fair-housing, or COPPA check — but there is no explicit statement of when to prefer this over `systemores_stress_test_agent`, `systemores_evaluate_drift`, or `systemores_audit_tool_integrity`. No exclusions or prerequisites are given.

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