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

Annotations are all false and provide no safety hints, so the description must carry behavioral disclosure and does so richly. It explains the claim_token return flow, rate limiting ('5 per identifier per day'), cost behavior ('doesn't count against your tool-call quota'), review cadence ('reads digests daily'), and content restrictions ('don't paste the end-user's prompt'). This goes far beyond the structured fields.

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 longer than typical but each sentence serves a distinct purpose: purpose, triggers, exclusions, formatting rules, claim_token mechanics, and rate limits. It is front-loaded with the core action, and the density is justified by the tool's multiple behavioral nuances. Not perfectly tight, but no wasted words.

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 lifecycle: how to file, what a claim_token is for, how to check status later, rate limits, scope boundaries, and content guidelines. An agent can confidently invoke this tool and handle subsequent retrieval without missing information.

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 value by instructing users to describe issues in terms of Pipeworx tools/packs and explicitly warns against pasting end-user prompts, which the schema does not mention. It also clarifies claim_token usage synergistically with the schema, giving a modest lift.

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 and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates concrete scenarios (bug, feature/data_gap, praise) and clearly distinguishes this from sibling tools like ask_pipeworx or discover_tools, which are about answering questions or finding tools, not reporting issues.

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 ('Use when a tool returns wrong/stale data (bug)...') and when-not-to-use guidance ('if the tool came from a different MCP server... file it with that server instead'). It also resolves ambiguity with 'Pipeworx tool names are the ones this connection lists,' providing a clear decision rule.

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