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

Annotations only state readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, leaving behavioral details to the description. The description adds many valuable traits: rate limiting ('Rate-limited to 5 per identifier per day'), non-quota impact ('Free; doesn't count against your tool-call quota'), return value behavior ('Filing without an account returns a claim_token'), and the team's daily digest process. This goes well 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?

The description is long but each sentence carries distinct information: purpose, usage categories, exclusion rule, claim_token workflow, team behavior, rate limit, and quota. It is front-loaded with the purpose and usage, followed by essential operational details. Slightly verbose but well-structured and not repetitive.

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?

For a tool with 4 parameters (0 required), a nested context object, no output schema, and annotations that don't indicate safety, the description fully compensates. It covers all usage cases, exclusions, token handling, rate limits, and operational details. Even the parameter semantics are enhanced via the claim_token example. No information gap remains.

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% with descriptions for all four parameters, so baseline is 3. The description adds meaning beyond the schema for claim_token: 'pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})' and 'Read the reply to a report you filed earlier: pass the pwfb_… token that filing returned, with no other arguments.' This clarifies usage semantics not present in the schema.

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 explicitly distinguishes itself from siblings by scoping feedback to 'tools served by this Pipeworx connection' and noting that issues with other servers' tools should be filed elsewhere.

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?

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).' Also gives clear exclusions: 'if the tool came from a different MCP server... we cannot fix it' and describes the alternative action. It further explains how to use the claim_token for follow-up, covering usage variants.

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