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

Annotations are all false and offer no safety hints, so the description carries full burden. It discloses rate limiting ('Rate-limited to 5 per identifier per day'), free usage ('doesn't count against your tool-call quota'), the claim_token flow ('Filing without an account returns a claim_token; pass it back later... to read whether it was fixed'), and team workflow ('The team reads digests daily'). These traits are not derivable from structured fields.

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 longer than average, but every sentence carries operational value—purpose, use cases, exclusion, message guidance, token flow, rate limit. It is front-loaded with the most important info (what it does, when to use) and structured logically. Minor redundancy exists (e.g., 'PLAINLY' not needed), but it remains easy to scan.

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?

With no output schema and non-informative annotations, this description must supply all context. It covers every aspect an agent needs: what to report, how to scope it, the claim_token lifecycle, rate limits, and a fallback for non-Pipeworx tools. It even anticipates the 'not sure?' case by advising that Pipeworx tool names are the ones this connection lists. This is exceptionally complete for a feedback tool.

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 baseline is 3. The description adds meaningful semantics beyond the schema: it explains the claim_token usage pattern with a concrete example (`pipeworx_feedback({claim_token:"pwfb_…"})`), instructs users not to paste end-user prompts, and specifies message style ('Be specific (which tool, what error, what data was missing)'). This exceeds schema descriptions without being redundant.

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 specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It enumerates concrete feedback types (bug, feature/data_gap, praise), clearly distinguishing this tool from sibling query/action tools. Even the title 'Send Pipeworx Feedback' is reinforced, leaving no ambiguity about the tool's role.

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?

The description 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 a strong exclusion: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.' This is textbook usage differentiation.

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