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

Goes far beyond the annotations by disclosing the claim_token workflow for tracking feedback, the daily digest review, rate limiting (5 per identifier per day), free usage, and quota exemption. This gives the agent critical behavioral context like the fact that filing without an account returns a token for later status checks.

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 long, every sentence earns its place by covering a distinct aspect: purpose, use cases, scope exclusion, token behavior, team process, rate limits, and cost. The structure is front-loaded with the core action and then flows logically from usage to mechanics, with no filler or repetition.

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?

This is a feedback tool with 4 parameters, all optional, and no output schema. The description supplies the missing context: return behavior (claim_token), lifecycle (daily review, status checking), restrictions (rate limit, scope), and the necessary distinction between Pipeworx vs foreign tools. It is fully self-contained and agent-actionable.

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 baseline is 3. The description adds meaningful semantics beyond the schema: it clarifies that claim_token should be used with no other arguments to read a previous report, instructs how to phrase the message ('in terms of Pipeworx tools/packs — don't paste the end-user's prompt'), and defines the relationship between feedback types. This extra nuance justifies above baseline.

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 verb and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It immediately distinguishes from siblings by describing the feedback purpose and explicitly scoping to Pipeworx tools, leaving no ambiguity about what this 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?

Provides explicit when-to-use guidance with concrete examples (bug, feature/data_gap, praise). It also gives a clear when-not-to-use exclusion ('if the tool came from a different MCP server... file it with that server instead') and even directs users to check the connection's tool list if unsure, making alternative handling explicit.

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