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

Annotations only indicate readOnlyHint=false. The description adds substantial behavioral context: rate-limited to 5 per identifier per day, free and does not count against tool-call quota, team reads digests daily, returns a claim_token when filed without an account, and warns not to paste end-user prompts. No contradiction with annotations.

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 average but front-loaded with the purpose and each sentence contributes necessary guidance (boundaries, claim_token, rate limit, feedback content rules). While dense, it is well-organized and avoids fluff; the only minor redundancy is repeating the claim_token usage already in the schema.

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?

Given there is no output schema, the description covers the return behavior (claim_token and later status check), operational limits (rate limit, free), scoping (only this Pipeworx connection), and content expectations. It is fully self-contained for an agent to decide when and how to use it 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?

The schema already covers 100% of parameters with descriptions, so the baseline is 3. The description adds extra meaning beyond the schema by explaining how to construct the message (in terms of Pipeworx tools/packs, not prompts) and clarifying the claim_token usage pattern (pass with no other arguments). This goes beyond pure schema repetition.

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 clearly states this tool reports feedback to the Pipeworx team (broken, missing, or praise) and explicitly scopes it to tools served by this connection, distinguishing it from sibling tools like ask_pipeworx or research tools. It names specific categories (bug, feature, data_gap, praise) with concrete examples, so the agent knows exactly what it is for.

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 (wrong/stale data, missing tool, praise) and when-not-to-use guidance (tools from other MCP servers, with the alternative action of filing with that server). It also explains the claim_token workflow and rate limiting, making the tool's usage context fully clear.

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