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

All annotations are false, so the description carries the full burden. It discloses rate limiting ('Rate-limited to 5 per identifier per day'), the claim_token flow ('Filing without an account returns a claim_token'), free/cost status ('Free; doesn't count against your tool-call quota'), and the async review process ('The team reads digests daily'). These behavioral details go beyond the schema and annotations, giving the agent a clear picture of side effects and expectations.

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 efficiently structured, front-loaded with the core purpose and then systematically covering scope, exclusions, token mechanics, rate limits, and cost. Every sentence earns its place; there is no redundant or filler content, keeping it appropriately sized for the tool's 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?

Given the tool has 4 params, a nested object, no output schema, and no annotation help, the description is remarkably complete. It covers return behavior (claim_token), usage boundaries, rate limits, cost, and content guidelines. It also addresses the 'Not sure?' identification question, making it self-sufficient 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?

The schema covers 100% of the 4 parameters with detailed descriptions, providing a baseline of 3. The description adds meaningful beyond-schema meaning: message composition guidance ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'), typical length ('1-2 sentences typical'), and clarifies the claim_token usage loop. These additions justify a score above baseline, though not 5 since the schema already handles most 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 clearly states the tool's purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist,' with specific triggers (bug, feature/data_gap, praise). It also explicitly scopes to Pipeworx-served tools and excludes tools from other MCP servers, distinguishing it from alternative feedback channels.

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: 'Use when a tool returns wrong/stale data...', 'when a tool you wish existed isn't in the catalog', and 'when something worked surprisingly well.' It also gives a clear exclusion with an alternative: 'if the tool came from a different MCP server... file it with that server instead.' Additional context on how to identify Pipeworx tools ('Pipeworx tool names are the ones this connection lists') and how to phrase feedback further supports proper usage.

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