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

With all annotations false, the description carries the full burden. It adds value by disclosing a financial impact ('Deducts from wallet upon approval'), but omits other important behaviors like approval requirements, reversibility, or what happens on failure. The single behavioral detail is useful but insufficient for full transparency.

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 a single sentence that efficiently conveys the purpose and a key behavioral aspect. Every word earns its place; 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?

Given no output schema, the description should cover return values and state changes. It only mentions a side effect (wallet deduction) but omits what the tool returns (e.g., ad request ID, status) and any preconditions or permissions. For a tool with nested objects and financial implications, more context is needed.

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 has 100% parameter description coverage, so the description need not add much. It does provide contextual tie-in for 'budget' (deducts from wallet), but overall adds little extra meaning beyond the schema's own descriptions. Baseline 3 is appropriate.

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 clearly states the action ('Create') and the resource ('ad distribution request'), specifying the target ('contacts in pool lists matching target demographics') and a key side effect ('Deducts from wallet upon approval'). It distinguishes itself from sibling 'create_*' tools by focusing specifically on ad requests.

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?

The description explicitly states the use case ('to send a message to contacts in pool lists matching target demographics'), making it clear when to use. However, it does not provide exclusions or mention alternatives (e.g., 'neuron_update_ad_request' for existing requests), which would enhance guidance.

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