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

The description goes well beyond the annotations (which only say readOnlyHint=false, no destructive hint). It explains the full behavioral contract: filing returns a `claim_token`, which can later be passed back to read status and resolution details; it's rate-limited to 5 per identifier per day; it's free and doesn't count against tool-call quota; and the team reads digests daily. This gives the agent a clear model of side effects and constraints without contradicting 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 relatively long (around 170 words), but every sentence contributes necessary operational detail: purpose, use cases, exclusions, token flow, rate limits, and team behavior. It is front-loaded with the core purpose and structured logically. A minor deduction for length because a few clauses could be tightened (e.g., 'Not sure?' clarification), but it remains appropriately sized for the tool's complexity.

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 fully explains what to expect (claim_token, later status reply) and covers all relevant operational aspects: when to use, when not to use, how to reference tools, constraints, and follow-up mechanics. This is complete for a feedback submission tool, with no obvious 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?

Schema description coverage is 100%, so baseline is 3. The description adds extra meaning by explaining the `claim_token` workflow explicitly (`pipeworx_feedback({claim_token:"pwfb_…"})` with no other arguments) and by providing practical guidance on message length ('1-2 sentences typical, 2000 chars max'). This adds value beyond the schema's field descriptions, making the parameter semantics clearer.

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 action: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It names the resource (Pipeworx team) and the verb (tell/feedback), and clearly distinguishes from sibling tools like ask_pipeworx, which are for asking questions rather than sending feedback. It also distinguishes from external server feedback by explicitly limiting scope to Pipeworx connection 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 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 concrete exclusion: tools from other MCP servers should be filed with that server, not here. This clearly directs the agent to the correct alternative behavior.

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