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

Annotations provide no safety hints (all false), so the description carries full responsibility. It discloses rate limiting (5 per identifier per day), that it is free and doesn't count against quota, the claim_token flow for anonymous filing, that digests are read daily, and that signals affect roadmap. This is rich behavioral disclosure 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?

Though the description is longer than average, every sentence earns its place: purpose, usage triggers, exclusions, framing guidance, claim_token mechanics, team process, rate limits, and cost. It is front-loaded with the core purpose and structured logically. No fluff or redundancy.

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 4 parameters (0 required), nested object properties, no output schema, and relatively involved follow-up behavior, the description covers all necessary ground: what feedback types exist, how to frame messages, what happens without an account, how to check resolution status, rate limits, and scope boundaries. It leaves no critical gap for an agent deciding whether to use this tool.

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 meaningful context beyond schema: it instructs users to describe issues in terms of Pipeworx tools/packs rather than pasting end-user prompts, and explains how to use claim_token for follow-up ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'). This significantly enhances parameter semantics.

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 statement: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It specifies the verb, resource, and scope, and clearly differentiates from sibling tools like ask_pipeworx (which queries information) and discover_tools (which lists tools). The supported feedback types (bug, feature, data_gap, praise) add further precision.

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 provides explicit when-to-use guidance for each feedback type ('Use when a tool returns wrong/stale data', 'when a tool you wish existed isn't in the catalog', 'when something worked surprisingly well'). It also gives a clear exclusion: tools from other MCP servers should be reported elsewhere, and advises how to identify Pipeworx tools. This is exemplary usage guidance.

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