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

Annotations already convey read-only, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral details beyond those annotations: the tool returns blocking violations and warnings, and it is a paid resource priced at $0.002 per call. No contradiction with annotations exists.

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?

Three sentences with no filler: function first, then scope/exclusions, then pricing. Each sentence earns its place, and the most important operational information is 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?

There is no output schema, yet the description only says 'returns blocking violations and warnings' without describing the response shape. The facts parameter is a freeform object with no examples or guidance, and the rules semantics are left mostly to the schema. The pricing and exclusion notes add useful context, but an agent still lacks enough detail to confidently construct a valid request for an arbitrary safety evaluation.

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 of explaining the two parameters. It only refers generically to 'caller-supplied facts' and 'caller-supplied rules' without explaining fact structure, rule syntax, severity defaults, or how fields and operators work. The schema itself provides the only real semantics for the rules array, and the facts object remains completely unspecified.

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 clear action ('Evaluates caller-supplied facts against explicit caller-supplied rules') and names the output ('blocking violations and warnings'). It also clarifies the domain ('execution safety') and excludes many adjacent domains. However, among the many execution_safety_policy_engine siblings, it offers no trait that differentiates this specific engine from its similarly named peers.

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?

Explicitly says when NOT to use it: not for legal, identity, sanctions, fraud, contractual, or regulatory adjudication. It also frames the intended use case as execution safety. It does not name a specific alternative tool to use instead, so it stops short of full when-to-use-versus-alternative guidance.

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