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

Annotations are all false hints and provide no safety/behavior signal, so the description carries the full burden. It discloses the claim_token mechanism, the daily digest cadence, rate limiting ('Rate-limited to 5 per identifier per day'), free/no quota impact, and the instruction not to paste end-user prompts. These are valuable behavioral traits beyond the schema.

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 moderately long but every sentence earns its place. It opens with the core purpose, then logically flows through when to use, exclusions, claim_token usage, operational details, and constraints. No fluff or repetition; structure is optimized for an agent scanning for relevance.

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 covers return value behavior (claim_token) and post-submission expectations. It addresses rate limits, free access, and the appropriate scope (Pipeworx-only tools). Combined with the schema's thorough parameter descriptions, the agent has everything needed to invoke this 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?

Even though schema coverage is 100%, the description adds essential parameter semantics: it explains the claim_token flow ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})') and enriches the message parameter ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'). This goes beyond the schema's field-level descriptions.

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 clear verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It elaborates with specific feedback categories (bug, feature/data_gap, praise) and explicitly distinguishes this from sibling tools by restricting it to Pipeworx-served tools and naming the alternative behavior (file with another server).

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?

Provides explicit when-to-use guidance: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also gives a clear exclusion: 'if the tool came from a different MCP server... file it with that server instead,' plus disambiguation on identifying Pipeworx tool names.

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