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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds a valuable behavioral guarantee—no paid service is invoked—and specifies the breadth of status information returned, which is not covered by the annotations.

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 a single, front-loaded sentence with no redundancy. It packs the action, the list of resources, and a key qualifier into a compact form, making it easy for an agent to parse quickly.

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?

For a read-only listing tool with strong annotations and full parameter schema coverage, the description provides enough detail to invoke correctly. It omits return structure, but the low complexity and the explicit scope make it sufficiently complete.

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?

The single parameter include_inactive is fully documented in the schema with a clear description (100% coverage). The tool description adds nothing beyond that, so the baseline score of 3 is appropriate.

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 the specific verb 'List' and clearly enumerates the distinct resources: Agoragentic execution verifiers, Argent/Themis high-risk posture, lifecycle states, and optional external verifier readiness. This precise scope distinguishes it from sibling tools focused on quoting, receipts, settlement, or service calls.

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 phrase 'without invoking a paid service' gives a clear context for when to use this tool—as a cost-free readiness check before potentially paid operations. However, it does not explicitly name alternative tools or state when not to use it, falling just short of full exclusion guidance.

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