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

Annotations are all false (not read-only, not open-world, not idempotent, not destructive), yet the description adds valuable behavioral context: anonymous filing returns a claim_token, rate limit of 5 per identifier per day, free and not counted against quota, and daily team review. These traits go far beyond what annotations convey and set clear expectations for the agent.

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 dense but every sentence earns its place. It is front-loaded with the main purpose, then logically moves through triggers, exclusions, message guidelines, claim token behavior, and rate limits. No redundancy or fluff; length is justified by the richness of required context.

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?

With no output schema, the description explicitly discloses the return behavior (claim_token for anonymous filing and how to use it to check resolution). It covers all usage contexts, exclusions, rate limiting, and quota impact, giving the agent a complete operational picture for a nuanced feedback tool with 4 parameters and nested context.

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% and each parameter already has detailed descriptions (e.g., claim_token explains the read-reply flow, message describes specificity and max length). The description reinforces claim_token usage and adds a crucial semantic cue: describe issues in terms of Pipeworx tools/packs, not end-user prompts. This one extra piece of guidance raises it above the baseline 3.

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, specific directive: 'Tell the Pipeworx team something is broken, missing, or needs to exist' and lists the exact feedback types (bug, feature/data_gap, praise). It explicitly scopes to tools served by this Pipeworx connection, distinguishing it from other MCP servers and filling a unique niche among sibling tools. No other sibling provides a feedback channel, so the purpose is unambiguous.

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?

Usage guidelines are explicit and comprehensive: it states when to use (bug, feature/data_gap, praise) and when not to use ('if the tool came from a different MCP server... file it with that server instead'). It also provides practical guidance on how to phrase feedback (describe in terms of Pipeworx tools/packs, do not paste the end-user's prompt), and explains the claim token flow. This fully satisfies the dimension.

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