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

With all annotations set to false, the description must carry the full burden of behavioral disclosure. It excels by detailing the claim_token workflow, rate limit (5 per identifier per day), cost (free, no quota), and how feedback is processed (daily digests, roadmap impact). It also advises against pasting end-user prompts. This is strong context, though it could mention the exact response format for a successful submission beyond the token.

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 front-loaded with the core purpose and usage, followed by crucial operational details. Every sentence earns its place: the scope limitation, claim_token mechanism, and rate limit are all essential for correct invocation. It is well-structured and free of fluff, though it could trim the motivational line about daily digests without losing utility.

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?

The description provides a complete picture for a tool with no output schema: it explains what the tool does, when to use it, how to scope feedback, the claim_token return flow, rate limits, and quota impact. It adequately covers the workflow and expectations. It does not describe the exact response envelope, but the claim_token mention suffices for a feedback tool.

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%, and each parameter already has a thorough description: the type enum explains each value, context clarifies its sub-fields, message describes content and length, and claim_token explains the read-back flow. The tool description adds a small extra by demonstrating claim_token usage inline, but the schema already carries the semantic weight. Baseline 3 for high coverage is appropriate.

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 and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly enumerates feedback types (bug, feature/data_gap, praise) and explicitly scopes to tools served by this Pipeworx connection, distinguishing it from any sibling tools. This leaves no ambiguity about what the tool does.

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 explicitly states when to use the tool ('Use when a tool returns wrong/stale data... when a tool you wish existed isn't in the catalog... or when something worked surprisingly well') and provides an alternative course of action for tools from other MCP servers ('file it with that server instead'). This is textbook usage guidance with clear exclusions.

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