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

Annotations provide no safety hints (all false), so the description carries full burden and excels. It discloses rate limiting ('5 per identifier per day'), that it's free and doesn't count against quota, the unauthenticated flow returning a claim_token for later retrieval, and instructs users to describe issues in terms of Pipeworx tools/packs while avoiding pasting end-user prompts. This far exceeds typical transparency expectations.

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?

Though the description is lengthy, every sentence serves a purpose: purpose, usage triggers, exclusion scope, feedback etiquette, claim_token mechanism, rate limits, and team process. It is front-loaded with the most critical information and maintains coherent logical flow without redundancy or fluff.

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 moderate complexity (4 optional params, nested object, no output schema), the description covers all critical contexts: how to file, what happens without an account, how to later retrieve status, usage boundaries, and constraints. It lacks nothing essential for an agent to correctly invoke and reason about the 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 covers 100% of parameters, so baseline is 3. The description adds no significant param-level detail beyond the schema; it mentions claim_token flow and general guidance, but the schema already thoroughly explains each parameter (type enum, context object, message constraints, claim_token usage). The description does not compensate for any schema gap because none exists, but it also doesn't add extra semantics beyond what structured fields provide.

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 phrase 'Tell the Pipeworx team something is broken, missing, or needs to exist,' clearly identifying the tool's resource (Pipeworx feedback) and action (send feedback). It further enumerates distinct feedback types (bug, feature/data_gap, praise), and distinguishes itself from sibling tools by explicitly scoping to Pipeworx-owned tools, preventing confusion with other MCP servers.

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 (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 and alternative: for tools from a different MCP server, 'file it with that server instead,' and gives a decision heuristic ('Not sure? Pipeworx tool names are the ones this connection lists').

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