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

Annotations are all false, so the description carries the burden of behavioral disclosure. It adds rich context: rate-limited to 5 per identifier per day, free, doesn't count against quota, returns a claim_token for later lookup, team reads digests daily, and warns against pasting end-user prompts. No contradiction with annotations; these details go well beyond the schema.

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 earns its place: purpose, when/why to use, exclusion criteria, formatting instructions, token mechanics, rate limits, and cost structure. It is front-loaded with the core purpose and scoped guidance, with no redundant or tautological content. Each sentence adds new, actionable information.

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 covers the return behavior (claim_token, status updates) and contextual constraints (rate limit, quota, exclusivity to Pipeworx tools). It explains the purpose of the nested context object and the enum semantics, making the tool fully understandable for an agent without further documentation. This is a complete description for a feedback tool.

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 parameters are already well-documented. The description enhances this by explaining how claim_token works ('Filing without an account returns a claim_token; pass it back later...'), how to describe issues in terms of Pipeworx tools/packs, and the semantics of the 'type' field through examples. This adds value above the schema, though the schema already does heavy lifting.

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 'Tell the Pipeworx team something is broken, missing, or needs to exist,' which clearly states the verb (tell/send feedback) and resource (Pipeworx team). It enumerates feedback types (bug, feature/data_gap, praise) and explicitly distinguishes itself from sibling tools like ask_pipeworx by focusing on reporting issues about the tools themselves, not asking questions.

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 use 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 gives strong when-not-to-use guidance: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.' This is model usage guidance with alternatives.

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