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

Annotations only mark readOnlyHint=false, destructiveHint=false, which are ambiguous. The description adds substantial behavioral detail: filing returns a claim_token for later follow-up, rate-limited to 5 per identifier/day, free, and the team reads digests daily. It also instructs not to paste end-user prompts, clarifying the expected content and side-effect nature.

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: purpose, triggers, exclusion, content guidance, claim-token follow-up, rate limit, and cost. It is front-loaded with the core purpose and structured logically, making it easy for an agent to parse.

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?

Given a 4-parameter input schema with nested objects and no output schema, the description covers all critical aspects: what this tool does, when to use it, what to include, how to follow up via claim_token, rate limits, and cost. It only omits explicit response fields for logged-in users, which is minor since filing without an account is the described common path.

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 baseline is 3. The description goes beyond the schema by explaining the claim_token workflow ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})'), giving message length guidance ('1-2 sentences typical, 2000 chars max' is in schema but also reinforced), and warning not to paste user prompts. This adds actionable semantics for the message parameter.

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?

Description opens with 'Tell the Pipeworx team something is broken, missing, or needs to exist,' clearly stating the action (submit feedback) and target (Pipeworx team). It distinguishes from sibling tools by emphasizing this is the dedicated feedback channel and explicitly scoping it to 'tools served by this Pipeworx connection,' unlike other research/query 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?

Provides explicit triggers: '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 a clear exclusion: 'if the tool came from a different MCP server in your client ... file it with that server instead,' plus a fallback heuristic: 'Not sure? Pipeworx tool names are the ones this connection lists.'

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