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

Annotations are all false (no positive hints), so the description carries the burden. It discloses rate limits ('Rate-limited to 5 per identifier per day'), free usage, the claim_token return mechanism, and the fact that the team reads digests daily. No annotation contradiction; the description makes the tool's side effects clear enough for an agent.

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 long but well-structured, starting with purpose and then moving into usage, exclusions, and follow-up. Every sentence provides meaningful information, though the roadmap comment ('signal directly affects roadmap') is somewhat motivational and could be trimmed. It remains appropriately sized for the tool's complexity.

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?

The description is comprehensive for a feedback tool, covering what it does, when to use it, exclusions, return behavior (claim_token), and follow-up usage. Since there is no output schema, it explains the return value well. Minor omissions like whether feedback is anonymous or tied to an account are not critical for an agent to invoke the tool correctly.

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 the baseline is 3. The description adds value by instructing users to 'Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt,' which clarifies the message parameter. It also provides a concrete claim_token usage example, enhancing the schema's description.

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-resource pair ('Send Pipeworx Feedback') and clearly explains it's for reporting broken, missing, or desired functionality. It also distinguishes from sibling tools by explicitly limiting scope to the current Pipeworx connection, so an agent can tell it apart from other feedback mechanisms.

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 explicit when-to-use guidance: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also gives when-not-to-use: 'if the tool came from a different MCP server... file it with that server instead,' including a disambiguation rule ('Not sure? Pipeworx tool names are the ones this connection lists').

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