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

The annotations provide no meaningful safety/behavior hints (all false), so the description carries the full burden. It discloses rate limiting (5 per identifier per day), that it's free and doesn't count against tool-call quota, the claim_token flow for anonymous tracking and later retrieval, and that the team reads digests daily. This goes well beyond the structured 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 a lengthy single paragraph, it is front-loaded with purpose and then systematically covers usage, exclusions, workflow, and limits without redundancy. Every sentence delivers actionable information; the length is justified by the rich operational context needed for a feedback tool with a token-recovery mechanism.

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?

The tool has no output schema, but the description explains the returned claim_token and how to use it. It also covers required context (which connection/tool), exclusions, rate limits, and the team's response process. This is fully sufficient for an agent to select and invoke the tool correctly in all described scenarios.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining the claim_token workflow (filing without an account returns a token, pass it back later to read status), and by advising users to describe issues in terms of Pipeworx tools and avoid pasting user prompts. It does not re-explain every parameter, but the schema already does that thoroughly.

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 specific verb ('Tell the Pipeworx team') and resource ('something is broken, missing, or needs to exist'), immediately defining the tool's purpose. It further distinguishes this tool from all siblings by scoping it to Pipeworx connection tools and naming concrete feedback categories (bug, feature/data_gap, praise).

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 guidance for each feedback type (bug, feature, data_gap, praise) and explicitly says when NOT to use it: for tools from a different MCP server, directing the user to file with that server instead. It also clarifies ambiguous cases by saying Pipeworx tool names are those this connection lists, and instructs users not to paste the end-user prompt.

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