audit_delivery_readiness

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

With no annotations, the description carries the full burden. It discloses that it runs all QA rules optionally filtered by ruleset and returns a scored verdict, indicating a read-only audit. However, it omits performance implications, error behaviors, or what 'loaded' means operationally.

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?

Two concise sentences accomplish the goal without waste. It front-loads the action and return value, using parenthetical detail for the optional filter—highly efficient.

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 presence of an output schema reduces the need to describe return values, and the description covers the core function. However, the unclear 'port' parameter and the meaning of 'loaded' rules create gaps that a bit more context could fill.

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 must explain both parameters. It addresses 'ruleset' by mentioning filtering by that tag, but 'port' is completely unexplained. This leaves half the parameters underspecified.

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 uses a specific verb ('Run') and resource ('all loaded QA rules') against 'the open model', returning a 'scored verdict'. It differentiates from sibling 'run_rule' (singular) by indicating a batch operation, and the optional 'ruleset' filter clarifies scope.

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 explicit when-to-use guidance or exclusions are provided. The description implies batch auditing but does not contrast with alternatives like 'run_rule' or 'verify_ifc_export_readiness', nor does it mention prerequisites such as rules being 'loaded'.

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