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

The description discloses many behaviors beyond the annotations: rate-limited to 5 per identifier per day, free and doesn't count against quota, the claim_token flow for tracking, and the instruction not to paste the end-user's prompt. It also explains what happens after submission (team reads digests daily, signal affects roadmap). This is rich behavioral context that the annotations (all false) do not provide.

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 dense but well-structured. It front-loads the core purpose, then flows into usage conditions, scope exclusions, submission guidelines, claim_token behavior, and rate limits. Every sentence adds information, though it could be slightly tightened (e.g., the 'broken, missing, or needs to exist' phrasing is then expanded into the type enum categories). Overall, efficient for the complexity.

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?

With no output schema, the description fully explains the return behavior (claim_token, how to read status and resolution). It also covers the full lifecycle: what to submit, how to track, what happens after (read daily, affects roadmap). For a feedback tool with no other output constraints, this is complete and self-sufficient.

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 schema already covers 100% of parameter descriptions, so baseline is 3. The description adds value with the claim_token usage semantics ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed') and the guidance to describe issues in terms of Pipeworx tools/packs rather than pasting user prompts. This goes beyond the schema's basic field descriptions, earning 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?

The description clearly states the action: tell the Pipeworx team something is broken, missing, or needs to exist. It distinguishes from siblings by emphasizing it is ONLY for tools served by this Pipeworx connection, and it enumerates categories (bug, feature, data_gap, praise) that map to the tool's purpose.

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?

Explicit 'Use when' conditions for each feedback type, plus a clear exclusion: if the tool came from a different MCP server, file with that server instead. Provides a concrete alternative ('file it with that server instead') and clarifies which tools are in scope ('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.