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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully states that no personal data should be captured and limits the payload to 'the idea, its category and the pain', plus notes the forward-looking nature of the demand. It doesn't describe storage, confirmation, or side effects, but the privacy boundary is a meaningful behavioral disclosure.

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 compact and front-loaded: purpose, examples, differentiation, trigger condition, and privacy constraint all appear in three dense sentences. Every sentence earns its place with no 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 simple intent-capture tool, the description provides the trigger, the closest sibling distinction, the captured data fields, and a privacy constraint. It doesn't specify the return/confirmation behavior or category values, but these are minor given the fire-and-forget nature of the tool and its small schema.

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 schema already describes all three properties, so the baseline is 3. The description reinforces the idea/category/pain fields but adds little semantic detail beyond the schema; notably, the category field's schema description appears identical to idea's, and the description doesn't clarify what category values are expected.

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 states a specific verb and resource: 'Capture a DESIRED TOOL idea', and gives concrete examples. It also explicitly contrasts itself with report_unmet_demand, making its purpose and scope unambiguous.

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 clearly says when to call it — 'when a user expresses a wish or a recurring pain that a tool could solve' — and explicitly names the alternative tool (report_unmet_demand) and the distinction between them. This gives an agent direct routing guidance.

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