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

Annotations provide only false hints, leaving the description to disclose behaviors. It adds valuable context: rate limiting ('Rate-limited to 5 per identifier per day'), cost ('Free; doesn't count against your tool-call quota'), and the claim_token workflow including that filing without an account returns a token and passing it back later reads resolution status.

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 a dense single paragraph but every sentence carries essential information: purpose, use cases, exclusions, content guidance, token flow, rate limit, and cost. It is front-loaded with the primary action. A slightly more structured layout (bullets or short paragraphs) would improve scannability, but it remains efficient and non-redundant.

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 the tool's purpose, usage triggers, exclusions, claim_token lifecycle, rate limiting, and content guidance. It explains what happens when filing without an account (returns claim_token) and how to retrieve status later. The richness of this description makes the tool fully understandable and 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 already has 100% parameter descriptions, so baseline is 3. The description adds meaningful usage semantics beyond the schema: instructs to 'describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt' for the message field, and demonstrates how to use claim_token with the syntax 'pipeworx_feedback({claim_token:"pwfb_…"})'.

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 immediately distinguishes this feedback tool from the sibling research/search tools by its unique purpose of reporting issues or praise about Pipeworx 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' guidance with enumerated cases: '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 states a clear when-not and alternative: 'ONLY for tools served by this Pipeworx connection... file it with that server instead.'

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