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

Annotations are all false (no hints), so the description carries full burden. It discloses rate limiting (5 per identifier per day), quota exemption (free, doesn't count against tool-call quota), the claim_token mechanism for later status checks, and the human process (team reads digests daily, signal affects roadmap). This goes far beyond the minimal safety profile and gives the agent accurate expectations.

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 dense but every sentence adds operational value: purpose, when-to-use, when-not-to-use, alternative action, claim_token mechanics, message guidance, team workflow, rate limit, and quota impact. It is front-loaded with the most critical information and has no redundant filler.

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 feedback tool with no output schema, no helpful annotations, a nested context object, and a subtle claim_token follow-up mode, the description covers all necessary aspects: how to categorize feedback, what context to include, what to avoid, the token workflow, rate limits, and cost. An agent can confidently invoke this tool without further clarification.

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 covers parameter names and types well, but the description adds essential semantics: claim_token is for reading a previous report's status and must be passed alone; message should describe issues in terms of Pipeworx tools/packs, not paste user prompts. This guidance prevents common misuse and clarifies the intended flow beyond what the schema states.

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 verb+resource ('Tell the Pipeworx team something is broken, missing, or needs to exist') and immediately enumerates concrete use cases (bug, feature/data_gap, praise). This clearly distinguishes it from sibling research and utility tools, which are about retrieving or analyzing data, not providing feedback.

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?

Explicit when-to-use guidance is given for each feedback type, plus a clear exclusion: if the tool came from a different MCP server, file with that server instead. It also explains the claim_token follow-up workflow, giving the agent a complete decision framework for using this tool vs. alternatives.

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