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

Beyond the all-false annotations, the description richly discloses behavior: anonymous submissions return a claim_token for later status checks, the team reads digests daily, rate limit is 5 per identifier per day, and it is free/does not count against quota. It also warns against pasting end-user prompts, adding practical behavioral context.

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 sentence carries essential operational information: purpose, use cases, exclusions, token mechanics, rate limits, and cost. It is front-loaded with the core purpose and organized logically, so length is justified by completeness rather than redundancy.

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 4-parameter, 0-required, nested-object tool with no output schema, the description covers everything an agent needs: when to use, what to include, token follow-up, rate limits, and scope boundaries. It is fully self-sufficient and complement the schema without repeating it.

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 baseline is 3, but the description adds real value beyond the schema: it explains the claim_token follow-up invocation pattern (pipeworx_feedback({claim_token:"pwfb_…"})) and instructs describing issues in terms of Pipeworx tools/packs, which meaningfully informs how to fill context and message. Slightly less value is added to the type and context parameters because the schema already defines them well.

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 clear, specific verb+resource statement ('Tell the Pipeworx team something is broken, missing, or needs to exist') and immediately distinguishes the tool from siblings by enumerating feedback types (bug, feature/data_gap, praise). It is unmistakably a feedback submission tool, not an ask or research tool.

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?

Provides explicit when-to-use guidance for each feedback type and a strong when-not-to-use exclusion: if the tool came from a different MCP server, file with that server instead. It even offers a disambiguation rule ('Pipeworx tool names are the ones this connection lists'), making selection unambiguous.

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