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

Annotations are generic (all false, no meaningful safety hints), so the description carries the full transparency burden. It discloses rate limiting ('Rate-limited to 5 per identifier per day'), quota exemption ('doesn't count against your tool-call quota'), the anonymous claim_token flow, content guidance (don't paste end-user prompt), and roadmap impact ('signal directly affects roadmap'). No contradiction 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 longer than average (9 sentences), but each sentence conveys a distinct operational rule: purpose, triggers, scope restriction, identification heuristic, prompt handling, token flow, roadmap impact, rate limit, and quota. It is front-loaded with purpose, and no sentence is redundant. The length is justified by the tool's boundary conditions, though it could be tightened slightly.

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 no output schema and moderate complexity (4 params, nested objects, enum), the description covers most relevant context: what the tool does, when to use, scope limits, token-based status checking, rate limit, and quota. It does not specify what a successful standard (account-based) submission returns, only the anonymous claim_token return. This small gap prevents a 5, but overall it is highly complete.

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 all four parameters, including enum meanings and the claim_token usage. The description adds a tiny bit by writing out the exact call syntax pipeworx_feedback({claim_token:"pwfb_…"}) and connecting the token flow, but this is largely supplemental to what the schema already states. Baseline 3 is appropriate.

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 imperative: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It explicitly names the resource (Pipeworx team) and the action (send feedback), and further differentiates from siblings like ask_pipeworx by framing it as a reporting channel rather than an information query.

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 gives explicit when-to-use triggers: '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 clear exclusion: 'if the tool came from a different MCP server... file it with that server instead,' plus a heuristic for identification ('Pipeworx tool names are the ones this connection lists').

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