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

Although annotations are all false and provide little signal, the description richly discloses behavioral traits: filing returns a claim_token for later lookup, rate-limiting is 5 per identifier per day, it is free and does not count against tool-call quota, and the team reads digests daily. It also explains the asynchronous resolution workflow. This goes well beyond the annotations and gives agents an accurate model of side effects and constraints.

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 about 150 words, but every sentence earns its place: purpose, use cases, exclusions, message guidance, token workflow, rate limits, and quota impact. It is front-loaded with the most important information and flows logically. It is not bloated; it is efficiently dense for a tool with this many nuances.

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?

Despite having no output schema, the description fully covers the tool's behavior: what to report, how to report it, the claim_token retrieval flow, rate limits, and scope boundaries. With nested objects, an enum, and a claim_token follow-up mechanism, the description leaves no significant aspect unexplained. It is complete for an agent to select and invoke correctly.

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 the baseline is 3. The description adds a valuable message-construction rule not present in the schema ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt') and contextualizes the claim_token lifecycle in a single workflow. However, most parameter meaning is already perfectly covered by schema descriptions, so the increment is modest but meaningful.

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 'Tell the Pipeworx team something is broken, missing, or needs to exist,' using a specific verb ('tell') and a clear resource (the Pipeworx team). It enumerates concrete use cases (bug, feature, data_gap, praise) and is cleanly distinguished from sibling tools, all of which are research/information tools rather than feedback submission. No ambiguity about what the tool does.

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 explicitly states when to use the tool (wrong/stale data, missing capability, praise) and when NOT to use it: if the tool came from a different MCP server, file it there instead. It also clarifies the scope ('ONLY for tools served by this Pipeworx connection') and offers a test for uncertainty ('Pipeworx tool names are the ones this connection lists'). This is exemplary usage guidance with clear alternatives and exclusions.

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