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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds that it returns blocking violations and warnings and notes the price, which is useful but not extensive. It does not contradict the annotations, and the bar is lowered by the strong annotation coverage.

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 concise and front-loads the core purpose. It includes necessary exclusions and pricing, but the phrase 'quality unknown' is vague and adds little. Overall it is well-structured and to the point.

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?

The tool is complex with nested objects and no output schema, so the description should explain the return format and usage details. It only says 'returns blocking violations and warnings,' which is vague. It also lacks examples of rule evaluation and does not differentiate from the many similar sibling tools, making it incomplete.

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 schema description coverage at 0%, the description must compensate for parameter meaning, but it only rephrases the parameter names ('caller-supplied facts' and 'explicit caller-supplied rules') without adding format, examples, or constraints. The schema provides some structure for rules, but facts remain undefined, and the description adds no value beyond the schema.

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 clearly states the tool evaluates caller-supplied facts against rules and returns blocking violations and warnings, which specifies a concrete verb, resource, and output. However, it does not differentiate from other policy engines in the sibling list (e.g., execution_safety_policy_engine_08f4a690), so it lacks explicit sibling distinction.

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 exclusions (not for legal, identity, sanctions, fraud, contractual, or regulatory adjudication) and states it is intended for execution safety, which gives context. However, it does not mention when to use this tool over its many siblings or name any alternative tools, and it includes pricing but no usage conditions.

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