Read notification do-not-disturb state

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

No annotations provided, so description carries burden. It discloses the key trait of being non-mutating, but doesn't describe return format, potential errors, or state representation. Given simplicity, a 3 is fair.

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?

Single concise sentence, front-loads the action and resource, then clarifies non-mutating nature. No waste.

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?

Overall simple tool, no output schema, so description should specify return value format; it doesn't. It's clear it reads a state but not what that state looks like. For a status tool, this is a minor gap, but completeness could be better.

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?

No parameters to document; schema is empty with 100% coverage vacuously. Per rule, baseline 4 for 0 parameters. Description adds nothing parameter-specific, which 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?

States a specific verb and resource: 'Read the Omarchy shell notification-silencing state'. Explicitly says 'without changing it' distinguishing it from mutating siblings like notification_dnd_set.

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 changing it' implies this is for reading status vs. setting, but doesn't name alternatives explicitly. Still, clear context that it's a read operation, and the sibling set includes notification_dnd_set for changes.

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