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

Annotations are all false/neutral, so the description carries the full burden. It reveals key behaviors: filing without an account returns a claim_token, passing the token later lets you read resolution status, rate-limiting exists (5 per identifier per day), and it does not count against tool-call quota. 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 entirely purposeful; it is front-loaded with the core action and then systematically covers scope, method, token mechanics, rate limits, and cost. A few phrases like 'signal directly affects roadmap' are motivational rather than essential, so it is not perfectly lean, but every operational sentence contributes.

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 has no output schema and uses a relatively free-form feedback model, the description is remarkably complete: it explains the categories, expected message specificity, the claim-token mechanism for follow-up, exclusions, rate limits, and quota impact. An agent has everything needed to invoke and follow up 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 baseline is 3. The description adds meaningful semantics beyond the schema by explaining the claim_token round-trip flow ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed') and by guiding message content ('describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'). This extra context earns a 4.

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?

Purpose is explicit: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' This is a specific verb+resource action that is clearly distinct from sibling tools like ask_pipeworx, deep_research, or discover_tools, which are research or catalog-related rather than feedback submission.

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?

Extremely detailed when-to-use guidance: bug, feature/data_gap, or praise. Explicitly states when NOT to use it (for tools from a different MCP server, file there instead) and provides inclusion criteria ('Pipeworx tool names are the ones this connection lists'). Also gives practical instruction about not pasting end-user prompts and notes the daily rate limit.

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