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

The description goes far beyond basic annotations by detailing critical privacy behaviors, such as ensuring anonymity, the exclusion of PII like names and IP addresses, and the redaction policy.

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?

While informative, the description is slightly dense, but every sentence provides unique, high-value information that isn't in the schema or annotations.

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 the sensitive nature of recording user needs, the definition is exceptionally complete, covering purpose, usage rules, and critical data handling protocols.

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?

The description reinforces the nature of the required inputs, explicitly stating that data sent must be generic and stripped of personal identifiers, providing essential guardrails for parameter population.

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 tool's purpose is extremely clear: to record a user's unmet need so that developers can discover what to build. This distinguishes it well from sibling tools like search_tools or get_tool_details which retrieve information.

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?

It provides a perfect 'when to use' scenario: call this tool when no other tool in the catalog satisfies the user's current request.

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