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

Annotations are all false and uninformative, but the description carries the full burden and does excellently. It discloses the rate limit ('5 per identifier per day'), the claim_token flow for anonymous filing, the fact that it's free and doesn't count against tool-call quota, and how feedback is consumed ('team reads digests daily'). No contradictions with annotations.

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 dense: each sentence provides distinct value (purpose, usage categories, exclusion, content rules, token flow, rate limit, cost). It is front-loaded with the core purpose and then elaborates. Slightly verbose, but no filler or redundancy.

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?

Given the tool's moderate complexity (4 params, no output schema, all optional), the description covers the full lifecycle: what the tool does, when to use it, exclusions, content guidelines, follow-up token mechanism, rate limit, and cost. An agent can invoke it correctly without additional documentation.

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?

All 4 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds value with an explicit claim_token usage example (pipeworx_feedback({claim_token:'pwfb_…'})) and explains the token's role in retrieving resolution status, which reinforces and extends the schema's parameter documentation.

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 opens with a clear, specific purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist,' and enumerates the feedback types (bug, feature, data_gap, praise). It distinguishes itself from sibling tools by being the only feedback channel among the listed Pipeworx 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?

Provides explicit when-to-use heuristics for each feedback type (bug, feature/data_gap, praise) and an explicit exclusion for tools from other MCP servers: 'if the tool came from a different MCP server ... file it with that server instead.' It also gives content guidance (describe in terms of Pipeworx tools/packs, don't paste the end-user prompt). This is textbook usage guidance.

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