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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds only that it returns the session's 'current state', which usefully implies a non-mutating snapshot but says nothing about error behavior for unknown/expired session ids or any auth requirements.

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?

A single well-formed sentence with the verb and identifying key front-loaded and zero filler. It is efficient, though its brevity borders on under-specification rather than trimming redundancy.

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 tool whose annotations cover the safety profile, the definition is functional but thin: with no output schema, the description could have sketched what 'current state' contains (quorum progress, approvals, expiry). The undefined query parameter and unknown-id failure mode are also left unaddressed.

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 nominally 100%, so the baseline is 3, and 'by id' merely restates the required id parameter. The opaque free-form 'query' bag is documented only as 'Optional query parameters', and the description does nothing to clarify what keys it accepts, so no value is added over 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?

States a specific verb ('Fetch'), resource ('quorum approval gate session') and keying ('by id'), so the agent knows exactly what the tool does. It does not, however, differentiate itself from the closely named siblings affix_gate_quorum_approve and affix_gate_quorum_start beyond the implicit read-vs-write split.

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?

There is no guidance on when to call this versus affix_gate_quorum_start (to create a session), affix_gate_quorum_approve (to advance one) or affix_gate_multifactor_get (a different gate family). No prerequisites, no post-approval polling hint, no exclusions.

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