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

Annotations only say it is a non-destructive, open-world, non-idempotent write; the description adds materially more — that the payload is human-visible plaintext rather than encrypted, that it incurs no charge and creates no public artifact, and that a specific OAuth scope is required. It does not discuss whether submissions can be edited or withdrawn, which is the main remaining behavioral gap given destructiveHint=false.

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?

Two tight sentences: capability/scope statement first, follow-up constraints second. Zero filler and the most decision-relevant facts (private, free, no public post, scope) are front-loaded.

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 10-parameter write tool with no output schema and thin schema descriptions, the definition is adequate but under-specified: it never covers most of the optional fields or what happens after submission (no return-value or follow-up hint such as get_agent_need/list_agent_needs). The core intent and privacy model are complete, the field-level guidance is not.

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?

With 10 parameters and only 30% schema description coverage, the description should carry the load, but it only loosely gestures at willingness_to_pay and the request_type categories. Nothing explains the capability vs. use_case distinction, the request_type enum values (problem_report, paid_pilot_interest, contact_request), delivery_interface, or expected_monthly_uses.

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?

States a specific verb (Send) plus the exact resource class (bounded private plaintext product requests, model/integration needs, willingness-to-pay data, feedback) and names the recipient (the operator). The clause 'no public post or purchase' separates it from publish_board_post and the buy_* family without the agent needing to open schemas.

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?

Gives a clear use context (routing private needs/pricing feedback to the operator) and negative guidance ('no public post, no purchase'), plus the prerequisite scope 'boards:report'. It stops short of naming the actual sibling alternatives (e.g. report_board_post for flagging content, list_agent_needs for reading back submissions), so the routing is implied rather than explicit.

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