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

The annotations already establish that this is a non-destructive but non-read-only, non-idempotent, closed-world operation. The description adds meaningful behavior beyond that: email addresses and phone numbers are removed before the note is kept, and it explicitly says nothing on any book is changed and nobody is emailed.

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 two tight sentences with no wasted wording. The core action and scope come first, followed by the important privacy and safety guarantees.

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 simple feedback-submission tool with fully documented parameters and no output schema, the description covers purpose, triggering situations, privacy handling, and the fact that no book state changes. An agent has enough information to decide when and how to use it.

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 description coverage is 100%, so all five parameters are already documented in the input schema. The description reinforces the note's purpose and brevity but does not add syntax or constraints beyond what the schema provides.

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 uses a specific verb and resource: it sends a short feedback note to the people who make Chorus. It clearly scopes the content to failed tools, unexpected results, uncovered requests, or unclear descriptions, which distinguishes it from all the book-related sibling tools.

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 gives clear when-to-use guidance by listing the situations that warrant feedback: a tool failed, returned something unexpected, a request no tool covers, or a description was unclear. It does not explicitly say when not to use it or name an alternative, but for a feedback channel there is no obvious sibling alternative.

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