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

Annotations are minimal (readOnlyHint=false etc.), but the description supplies behavioral context beyond them: rate limiting ('Rate-limited to 5 per identifier per day'), quota impact ('doesn't count against your tool-call quota'), the claim_token flow ('Filing without an account returns a claim_token; pass it back later...'), and that the team 'reads digests daily and signal directly affects roadmap.' 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 long, but it covers multiple complex aspects (types, exclusions, token flow, rate limits, quota). Every sentence is informative; however, a few sentences like 'The team reads digests daily and signal directly affects roadmap' are motivational rather than directly actionable, and the block is one dense paragraph without structural breaks. It earns a 4.

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 the tool's complexity (four parameters, optional claim_token, multiple feedback types) and the absence of an output schema, the description provides complete coverage: purpose, when/when-not, token semantics, rate limits, and expected response behavior. An agent can use it correctly without further clarification.

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?

Although the input schema already describes all four parameters (100% coverage), the description adds important usage semantics: it clarifies the claim_token usage pattern ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), explicitly instructs users to 'Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt,' and explains that claim_token can be used 'with no other arguments.' This goes beyond the schema's per-parameter 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 'Tell the Pipeworx team something is broken, missing, or needs to exist,' which is a clear verb+resource statement. It explicitly enumerates the feedback types (bug, feature, data_gap, praise) and distinguishes this from sibling tools like ask_pipeworx or query by framing it as reporting issues about Pipeworx itself.

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 states exactly when to use: '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 an explicit exclusion: 'if the tool came from a different MCP server... file it with that server instead.' This satisfies 'explicit when/when-not/alternatives.'

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