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

With no annotations, the description carries the full disclosure burden. It does reveal one meaningful side effect — on failure a draft is queued — but says nothing about idempotency, whether that draft is persisted/email/queue item, permission requirements, or the return payload.

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?

One compact line, front-loaded with the role, with no filler. However the compression goes too far — 'PARITY' and 'draft queued' are compressed into undefined shorthand, making the line cryptic rather than 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?

No output schema exists, so the description must carry return semantics; it only vaguely gestures at GO/NO-GO and an artifact on failure. It omits what 'valid PARITY' means, what the draft contains, and where it goes — significant gaps for a gating tool whose decision drives downstream scheduling.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify about inputs, and it does not waste words inventing any.

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?

It names a specific role ('Scheduler gate') and the two outcomes (GO / NO-GO plus a queued draft), which is more than a tautology. But 'PARITY' is an undefined term and there is no explicit differentiation from the siblings parity_probe and parity_verdict, so an agent cannot tell from the text alone which one to pick.

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 statement of when to use this gate versus parity_probe or parity_verdict, nor any prerequisite (e.g. whether a probe must run first). Usage is only implied by the phrase 'Scheduler gate'.

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