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

Annotations are minimal (all false), so the description carries the full burden. It discloses rate limiting ('Rate-limited to 5 per identifier per day'), cost ('Free; doesn't count against your tool-call quota'), and return behavior ('Filing without an account returns a claim_token') plus how to use that token later. It also explains the human review process ('team reads digests daily and signal directly affects roadmap'). This goes well beyond 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, but every sentence serves a purpose: scope definition, use-case enumeration, exclusion criteria, token workflow, rate limiting, and roadmap impact. It front-loads the primary purpose and then delivers necessary operational details. Slightly verbose in the middle ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt') but that guidance is valuable for correct use.

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 tool with no required parameters and no output schema, the description fully equips the agent: it explains what counts as valid feedback, how to scope the context (tool/pack/vertical), how to read previous submissions, and what rate limits apply. The absence of an output schema is mitigated by the claim_token explanation. All important behavioral and workflow aspects are covered.

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 description coverage is 100%, so baseline is 3. The description adds workflow context by explaining how claim_token is obtained and used ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), but most parameter semantics are already richly documented in the schema. No parameter is left ambiguous; the description complements rather than compensates.

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, specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It explicitly names the feedback categories (bug, feature/data_gap, praise), distinguishing this tool from all sibling research/query tools. The scope constraint ('ONLY for tools served by this Pipeworx connection') further clarifies its unique 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?

Usage guidance is explicit and actionable: '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 explicitly excludes tools from other MCP servers and directs the user to file with that server instead, preventing misuse. It also clarifies how to interpret ambiguous cases ('Not sure? 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.