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

The description reveals several behavioral traits not present in annotations: the return of a claim_token when filing without an account, the later use of that token to check status, a rate limit of 5 per identifier per day, and that it is free and does not count against tool-call quota. This goes well beyond the generic false annotation values.

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 each sentence earns its place, starting with the core purpose and then flowing through usage rules, examples, claim_token flow, and operational details. The structure is front-loaded and scannable, though the note about roadmap signaling is somewhat tangential.

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?

For a feedback tool with no output schema, the description is highly complete: it specifies content expectations, categorization, exclusions, the claim_token lifecycle, rate limits, and cost/quota impact. It covers both initial filing and later follow-up, leaving no major operational gaps.

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 has 100% coverage with per-parameter descriptions, so the baseline is 3. The description adds meaningful usage semantics for the claim_token parameter by showing the exact invocation pattern (pipeworx_feedback({claim_token:'pwfb_…'})) and explains that passing only the token reads the reply. It also guides context structure with examples, adding value beyond the schema.

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 the specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist' and elaborates with concrete categories (bug, feature, data_gap, praise). It clearly distinguishes itself from sibling ask/discover tools by stating it is feedback for the Pipeworx connection itself.

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?

It provides explicit when-to-use guidance for each feedback type and concrete when-not-to-use guidance: tools from a different MCP server should be filed with that server instead. It also offers a fallback rule ('Not sure? Pipeworx tool names are the ones this connection lists.') and clarifies the tool is free and rate-limited.

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