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

Even though annotations are all false (no useful hints), the description discloses rich behavioral context: rate-limited to 5 per identifier per day, free and doesn't count against quota, returns a claim_token that can be used later to read resolution status, and team reads digests daily. It also warns against pasting end-user prompts, which is a practical behavioral constraint not captured in 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?

Though longer than a one-liner, every sentence serves a purpose: purpose, when-to-use, scope exclusion, claim-token mechanism, roadmap impact, rate limit, and quota exemption. The description is front-loaded with the core purpose and avoids redundancy, making it appropriately sized for the behavioral complexity it conveys.

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, the description must convey return behavior, and it does: 'Filing without an account returns a claim_token' and 'pass it back later... to read whether it was fixed and what changed.' It also covers rate limits, alternatives, and structured context (tools/packs), leaving the agent fully equipped to use the tool correctly without needing to infer anything.

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?

The input schema already provides 100% coverage with detailed descriptions for every parameter, so the baseline is 3. The description adds value beyond the schema by giving a concrete example of claim_token usage ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})') and by framing the type values within real use-case narrative, which helps an agent choose correctly. This extra guidance justifies a 4 rather than a 3.

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 verb+resource ('Tell the Pipeworx team something is broken, missing, or needs to exist') and then enumerates concrete categories (bug, feature/data_gap, praise). This distinguishes it from all sibling research, search, and subscription tools, making the tool's purpose unmistakable.

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?

Usage conditions are explicitly stated: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog... or when something worked surprisingly well (praise).' It also provides a clear exclusion for non-Pipeworx MCP servers and directs users to file with that server instead, which is exactly the kind of when-to-use vs. when-not-to-use guidance needed.

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