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

With annotations all false, the description carries the burden of disclosure and does so richly. It reveals rate-limiting ('Rate-limited to 5 per identifier per day'), the asynchronous claim_token flow ('Filing without an account returns a claim_token; pass it back later ... to read whether it was fixed'), and non-consumption of quota ('doesn't count against your tool-call quota'). It also discloses the team's review cadence, making behavior transparent beyond the 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?

Although the description is long, it is densely packed with actionable information and logically structured: purpose, when-to-use, exclusion, content rules, token mechanics, and operational details. Every sentence earns its place, and the opening front-loads the primary function. This is appropriate conciseness for the tool's complexity.

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?

With no output schema, the description explains the return behavior (claim_token and status reading), covers both usage modes (filing and checking), and addresses constraints like rate limits and quota. It also clarifies the expected content format, making it complete for a tool with 4 params and no output schema.

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 crucial semantics beyond the schema: the mutual exclusivity of claim_token ('with no other arguments'), the content guidance ('don't paste the end-user's prompt'), and the tool/pack oriented context. This extra info lifts it above baseline, though not to a 5 because the schema already defines each parameter's purpose.

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 clearly states the tool's purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It uses a specific verb ('tell') and resource (Pipeworx team), and distinguishes from sibling tools like ask_pipeworx by framing this as feedback rather than querying, plus explicitly scoping it to 'tools served by this Pipeworx connection.'

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: '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 gives a clear exclusion: 'if the tool came from a different MCP server ... file it with that server instead,' with a heuristic for identifying Pipeworx tools. This is textbook usage-guideline quality.

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