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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful context beyond annotations: it identifies included data such as production.alerts for depleted provider credits, states there is no generation or publication mutation, and warns not to claim delivery without a phone receipt. The instruction to notify the editor by text sits awkwardly beside a read-only annotation, but it reads as post-call agent guidance rather than a hidden side effect of this 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?

The description is front-loaded with the operator-only constraint and the core read action, which is good. However, it packs several operational protocols into run-on sentences, including text notification, deduplication by alert id, and phone receipt rules. Some of that wording is not directly about invoking this read-only tool and could be trimmed.

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 one-parameter read-only status tool with no output schema, the description covers what data is returned and what is out of scope. Annotations already cover the safety and idempotency profile, and the schema fully documents the date parameter. The only minor gap is that the text-notification instruction could be read as tool behavior rather than follow-up guidance.

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 coverage is 100% and the single date parameter already documents the Pacific YYYY-MM-DD format and the brief/status default differences. The description does not add any parameter-specific meaning beyond that. The baseline of 3 is appropriate because the schema carries the full parameter burden.

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 a specific verb and resource: read the saved OffStereo edition production status, substitutions, and held pitches. It distinguishes the tool from generation and publication mutation, though it does not name a sibling alternative explicitly. The purpose is clear without opening the schema.

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?

It establishes an operator-only constraint and says to report actionable failures or substitutions, which implies when to use the result. However, it gives no explicit guidance on when to use this tool versus related status, brief, or session tools. The notification instructions are operational follow-up guidance rather than tool-selection guidance.

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