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

Annotations only set all hints to false, so the description carries the burden and fully delivers. It discloses that filing without an account returns a claim_token, how to later use that token to read status, the 5/day rate limit, that it's free and doesn't count against tool-call quota, and that the team reads digests daily. No contradiction with annotations.

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: scope, exclusions, workflow, rate limits, and expected usage. It is front-loaded with purpose and usage, then flows into mechanics and constraints. Nothing is wasted, and the density is justified for a tool that needs to prevent misfiled feedback.

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?

Despite having no output schema, the description fully covers what to expect (claim_token, later status read), the constraints (rate limit, quota), and the exact scope boundaries. It tells the agent how to identify whether a tool belongs to Pipeworx and what to do otherwise, making the tool self-contained for correct invocation.

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%, so baseline is 3. The description adds meaningful guidance beyond the schema: it explains the claim_token round-trip workflow, gives message length/format guidance (1-2 sentences, 2000 chars), and clarifies that context is optional structured context. This extra value warrants a 4.

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 resource and action. It also enumerates feedback categories (bug, feature/data_gap, praise), which distinguishes it from sibling tools like ask_pipeworx or discover_tools.

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 criteria ('when a tool returns wrong/stale data... when a tool you wish existed isn't in the catalog... when something worked surprisingly well') and an explicit exclusion: 'ONLY for tools served by this Pipeworx connection' with instruction to file elsewhere for other MCP servers. It also tells the agent what to include ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt').

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