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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine business context beyond structured fields: unanswered questions block a release, and the call returns the entire conversation, not just the question text.

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?

Three front-loaded sentences that carry the resource, the blocking rule, and the filter rule with little waste. The middle sentence about unanswered questions blocking release earns its place as motivating context.

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-only, two-optional-param tool with no output schema, the description adequately conveys what is returned (questions plus the whole conversation) and both filter modes. A slightly clearer statement of the default behavior would close the remaining gap.

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%, so both parameters are already documented in the schema (including the same 'omit for open questions' rule). The description adds only the note that a release_id call includes closed conversations, which is marginal 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 (retrieve) and resource (reviewer questions about the artist's releases) and clarifies that the full conversation is returned, making it clearly distinct from the write-oriented answer_release_question. However, it never explicitly names the sibling it contrasts with, so an agent must infer the read-vs-answer 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?

Provides the practical filter rule ('Omit release_id for every open question') and explains why the data matters (an unanswered question blocks release), which implies when to reach for it. But there is no explicit when-to-use comparison against alternatives like answer_release_question or list_release_todos.

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