athena_deployment_assess_quiescence

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

With no annotations provided, the description carries full disclosure burden. It goes beyond typical promise semantics by clarifying that PASS validates only the evidence, not the actual system state, and enumerates non-effects (no fencing, no stopping writers, no snapshot verification, no production contact). This is exceptional transparency for a quiescence assessment tool.

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 sentences with zero waste. The first sentence defines the core function, the second sentence crisply delivers critical limitations. Every clause carries meaning, and the negative list is each a separate important exclusion, not filler.

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 moderately complex (4 required params, nested objects, no output schema), and the description covers purpose, scope, constraints, and side-effect exclusions. It lacks details on return value format and exact matching behavior, but the description is sufficient for an agent to decide whether to invoke it and likely accept the validated PASS semantics. The absence of output schema and annotations increases needed context, but the description still covers the essential operational envelope.

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%, but the description introduces meaningful semantic framing: 'exact current-image and state-snapshot coordinates' maps conceptually to the expected_current_image_ref and expected_state_snapshot_ref parameters, and 'single-writer quiescence observation' contextualizes the observation object. However, it does not explain the digest parameter's role or specific constraints beyond what the schema states (minLength 64).

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 ('Evaluate') with a precisely scoped resource ('a supplied single-writer quiescence observation against exact current-image and state-snapshot coordinates'). It also explicitly names the result semantics ('PASS validates supplied evidence only') and lists what the tool does NOT do, which distinguishes it from sibling deployment assessment tools like 'athena_deployment_assess_canary' or 'athena_deployment_validate'.

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 states what validation PASS covers ('supplied evidence only') and explicitly lists exclusions: 'it does not stop a writer, install a fence, verify a snapshot, or contact production.' This gives an agent clear when-to-use/when-not-to-use guidance and helps rule it out for operations that need actual enforcement or production contact.

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