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

Annotations are all false and carry no safety hints, so the description adds essential behavior. It discloses that filing without an account returns a claim_token and that passing that token later retrieves resolution status. It also notes 'Rate-limited to 5 per identifier per day' and 'Free; doesn't count against your tool-call quota.' 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?

Though a single dense paragraph, every sentence earns its place: purpose, use triggers, exclusion, claim_token mechanics, team cadence, rate limit, and quota impact. It front-loads the primary action and follows a logical flow, though it could benefit from bullet points for even easier scanning.

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 compensates by explaining return behavior: 'Filing without an account returns a claim_token' and later retrieval gives 'the status and, once resolved, what actually changed.' It also covers both operation modes, rate limiting, quota, and team response time. A minor gap is not stating what happens if called with no arguments, but all parameters are optional per 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?

With 100% schema description coverage, the baseline is 3. The description adds practical semantics beyond the schema: 'don't paste the end-user's prompt' for message, the claim_token retrieval pattern with an example, and the context object's purpose for structuring feedback. This enriches parameter understanding beyond the field descriptions.

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 imperative: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates exact categories (bug, feature, data_gap, praise) and clarifies scope by stating 'ONLY for tools served by this Pipeworx connection,' which clearly distinguishes it from sibling tools like ask_pipeworx and any other MCP server 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?

Explicitly states when to use: '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 an explicit exclusion and alternative: 'if the tool came from a different MCP server... file it with that server instead.' This provides clear when/when-not guidance with a named alternative.

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