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

Annotations are all false, so the description carries the full burden. It discloses the claim_token workflow (anonymous filing returns a token, pass it back to read status/resolution), rate limiting ('5 per identifier per day'), and resources (free, no quota impact, daily digest). It also explains the reporting scope restriction. These go far beyond 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 a single dense paragraph but every clause adds a distinct fact: purpose, use cases, scope exclusion, claim_token flow, rate limit, and cost. It is front-loaded with the primary verb and resource. Though longer than the two-sentence ideal, it efficiently packs necessary context without waste.

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, a nested context object, and no output schema, this description is complete. It explains when to use each feedback type, the claim_token retrieval mechanism (including what the response returns: status and changes), and constraints like rate limiting. No essential behavior is left uncovered.

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 schema already documents every parameter. The description adds behavioral context beyond the schema, especially for claim_token: 'pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})' and clarifies it should be used with no other arguments. It also maps feedback types to enum values via usage guidance, adding semantic clarity.

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 the exact action: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It names the resource (Pipeworx team) and explicitly enumerates the feedback types (bug, feature/data_gap, praise). This distinguishes it from all sibling tools, which are research/Notion operations.

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 precise when-to-use instructions: '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 an explicit exclusion: 'if the tool came from a different MCP server... file it with that server instead', naming the alternative course of action.

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