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

Beyond the annotations (which are all false and provide no safety hints), the description discloses important behavioral details: filing returns a `claim_token` that can be used later to check status, rate-limit of 5 per identifier per day, no quota impact, and that the team reads digests daily. This gives agents a complete picture of side effects and follow-up behavior.

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 longer than average, every sentence earns its place: purpose, usage, exclusions, follow-up, rate limits, and quota are all covered without redundancy. The description is front-loaded with the core purpose and structured so that critical constraints (e.g., only for Pipeworx tools) appear early.

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?

This tool has 4 parameters, no output schema, and uninformative annotations (all false), so the description must carry full weight. It covers what the tool does, when to use it, what to include, the return behavior (claim_token), and limitations (rate limit, quota). This is comprehensive for a feedback/submission tool and leaves no major operational gaps.

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 already provides 100% coverage of all 4 parameters, so the baseline is 3. The description adds valuable extra semantics, particularly for `message` (e.g., 'don't paste the end-user's prompt') and `claim_token` (the workflow of passing it back later), which elevates it above baseline but does not fully reinvent parameter documentation.

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 direct, specific statement: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' This clearly defines the tool's purpose and distinguishes it from sibling tools like ask_pipeworx, which are about asking questions rather than providing feedback.

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 for tools from other MCP servers and points to the appropriate alternative ('file it with that server instead').

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