enoch_queue_alert_check

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

The description only mentions the dry_run default, but does not disclose what happens when dry_run is false, any side effects, or authorization needs. Annotations provide readOnlyHint=false but no additional context.

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 are concise, but the first sentence is vague and the second adds only default information. Not enough substance to earn its place.

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?

Given 8 parameters, no output schema, and many sibling tools, the description lacks essential details about return values, behavior, and parameter usage, making it incomplete for reliable selection and invocation.

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?

With 0% schema description coverage and 8 parameters, the description only notes the dry_run default. No explanation of other parameters like requested_by, lane_key, etc., leaving the agent with minimal guidance.

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 states it runs 'queue alert/stale-active reconciliation', which is somewhat specific but uses jargon and does not differentiate from similar siblings like enoch_queue_health or enoch_reconcile_stale_lane.

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 guidance on when to use this tool versus alternatives. Does not mention any prerequisites, conditions, or exclusions.

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