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

Though annotations indicate this is not read-only/idempotent/destructive, the description adds substantial behavioral context: rate limit ('5 per identifier per day'), quota exemption ('doesn't count against your tool-call quota'), the claim_token flow for anonymous reports, how to later retrieve resolution status, and the human impact ('team reads digests daily and signal directly affects roadmap'). No annotation contradiction exists.

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 tightly packed: each sentence adds a distinct, non-redundant fact (scope, triggers, exclusions, token flow, rate limits, roadmap). It is front-loaded with purpose and then proceeds logically through usage, constraints, and feedback mechanics. No filler or repetition.

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 four parameters, nested context object, anonymous claim flow, rate limits, and cross-server boundary conditions, the description covers every relevant aspect. It explains what happens on submission (returns claim_token), edge cases (without account), follow-up (claim_token retrieval), and practical constraints (5/day, free). No output schema exists, but the description compensates fully.

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% with detailed descriptions, so baseline is 3. The description goes beyond by explaining the claim_token round-trip pattern ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), reiterating that claim_token requires no other arguments, and adding message best practices ('Be specific... 1-2 sentences typical'). This elevates it slightly above schema-only.

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+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates concrete trigger conditions (bug, feature/data_gap, praise) and explicitly delineates scope ('ONLY for tools served by this Pipeworx connection'), clearly distinguishing it from sibling tools like ask_pipeworx or deep_research.

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...') and exclusions ('if the tool came from a different MCP server... file it with that server instead'). It even names the alternative action (file with that server) and clarifies how to identify Pipeworx tools, leaving no ambiguity.

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