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

Annotations only set all hints to false, providing no side-effect information. The description compensates by disclosing the claim_token flow, daily rate limit of 5 per identifier, that it's free, doesn't count against tool-call quota, and that the team reads digests daily. 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 every section earns its place: purpose, usage scenarios, scope restriction, token mechanism, rate limit, and cost. It's front-loaded with the main purpose and structured sequentially. Slightly verbose but justified by 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?

With no output schema, the description covers all essential aspects: what the tool does, when to use it, what to write, how the claim_token works, and limitations. It even explains why reporting other servers' issues here is counterproductive. This is fully complete for an agent to invoke 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?

Schema already covers all four parameters with detailed descriptions, giving a baseline of 3. The description adds practical usage semantics for `message` ('describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt') and for `claim_token` (pass it later to read the resolution), which goes beyond the schema's basic 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 explicitly states 'Tell the Pipeworx team something is broken, missing, or needs to exist,' which is a specific verb and resource. It also enumerates feedback types (bug, feature/data_gap, praise) and is clearly distinct from sibling tools like ask_pipeworx or research 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 gives 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 provides a clear exclusion: 'if the tool came from a different MCP server in your client... file it with that server instead.'

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