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

Annotations only provide generic hints (readOnlyHint=false, etc.), so the description carries the burden of behavioral disclosure. It reveals concrete behaviors: rate-limited to 5 per identifier per day, free, doesn't count against tool-call quota, team reads digests daily, and the claim_token workflow for retrieving resolution status. These are valuable beyond any structured annotation.

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 long, but every sentence contributes value: purpose, usage criteria, exclusion, message guidance, claim_token mechanics, rate limits, and roadmap impact. It is front-loaded with the core function and maintains logical flow. It could be slightly tightened, but it is not verbose for the amount of important context it conveys.

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?

For a feedback tool with no output schema, the description is exceptionally complete. It covers what to report, when, when not to, how to write the message, how to track a report via claim_token, rate limits, and the fact that it's free. The sibling list includes other feedback-adjacent tools (linear_create_issue), but the description preemptively resolves ambiguity about which server's tools are eligible.

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 meaningful guidance for the message parameter ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt') and a concrete usage example for claim_token ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), which enriches the schema's terse 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 specific verb-plus-resource statement: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly differentiates this from siblings like ask_pipeworx (asking questions) and linear_create_issue (creating a tracked issue), by emphasizing it is exclusively for feedback about Pipeworx tools.

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 explicitly states when to use the tool: '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 provides a clear exclusion: 'if the tool came from a different MCP server... file it with that server instead.' This gives both positive and negative guidance.

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