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

The description discloses far more than the annotations convey. It explains the return token flow ('Filing without an account returns a `claim_token`; pass it back later... to read whether it was fixed and what changed'), rate limiting ('Rate-limited to 5 per identifier per day'), and side effects on roadmap ('signal directly affects roadmap'). It also tells users what not to do ('don't paste the end-user's prompt'), adding behavioral context the annotations lack.

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 longer than average but every sentence earns its place. It is front-loaded with the core purpose and then proceeds logically through usage, exclusions, token flow, and rate limits. While it could be trimmed slightly, the structure is clear and the length is justified by 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 carries the burden of explaining return values. It does so thoroughly: 'Filing without an account returns a `claim_token`; pass it back later... to read whether it was fixed and what changed.' It also covers all parameter usage, constraints, and the tool's scope, making it fully complete for an agent to use correctly.

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 the baseline is 3. The description adds meaning beyond the schema by explaining the claim_token lifecycle (how to use it to check status) and elaborating on the message parameter ('Describe the issue in terms of Pipeworx tools/packs'). It also clarifies the enum values with examples. This lifts the score above baseline.

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 clear verb and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It further scopes the tool to 'this Pipeworx connection' and explicitly distinguishes it from sibling tools that answer questions or explore data. It even provides exclusion guidance for tools from other MCP servers, making the purpose unmistakable.

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 gives explicit when-to-use criteria: '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 when NOT to use it: if the tool came from a different MCP server, 'file it with that server instead.' This is excellent, actionable guidance that prevents misuse.

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