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

Annotations are all false and provide no safety profile, so the description carries the full burden. It discloses rate limits ('Rate-limited to 5 per identifier per day'), quota independence ('doesn't count against your tool-call quota'), and the claim_token mechanism, including how to retrieve status later. It also states the team reviews digests daily, making side effects and expected response behavior clear.

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 front-loaded with purpose and followed by logically ordered sections: usage categories, exclusions, content guidelines, and operational details. Every sentence contributes unique information, and the length is justified by the tool's claim_token and rate-limit complexity. It could be slightly tighter, but nothing is wasted.

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 nested context, no output schema, and unhelpful annotations, the description is self-sufficient. It covers all invocation scenarios, exclusions, token handling, rate limits, and content best practices. An agent has everything needed to decide when to call and how to construct arguments 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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantic guidance: it instructs the agent to describe issues in terms of Pipeworx tools/packs and specifically not to paste the end-user's prompt. It also demonstrates claim_token usage with an example call, which goes beyond the schema's static description. This adds value without redundancy.

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 differentiates from sibling tools by scoping exclusively to Pipeworx tools and explicitly stating that issues with other MCP servers should be filed elsewhere. This is unambiguous and action-oriented.

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 explicit when-to-use guidance with concrete categories (bug, feature, data_gap, praise) and a clear exclusion rule: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.' It even offers a fallback for uncertainty ('Not sure? Pipeworx tool names are the ones this connection lists.'). This is exemplary usage guidance.

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