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

Annotations cover the safety profile (not read-only, open-world, non-idempotent, non-destructive), so the description only needs to add beyond that. It does: 'a person reads every message' reveals human review, 'one message' signals a single-fire non-idempotent behavior consistent with the annotation, and 'Free' discloses cost. It stops short of stating whether a submission can be withdrawn or needs a contact for a reply.

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?

Purpose, trigger, exclusion, and an illustrative example are packed into a few sentences with the core action front-loaded. The example consumes some length but earns its place by demonstrating the parameter shape; nothing reads as 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?

With 7 parameters and an output schema present, the description supplies the trigger, the exclusion, human-review context, and a concrete example, so an agent has what it needs to call correctly. Minor gaps remain around whether a contact is required for a reply and what happens after submission, but the output schema carries the response shape.

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 description coverage is 100%, so the baseline is 3 and the schema already documents each field including the topic enum and string formats. The embedded JSON example goes beyond the schema by showing fields used together in a realistic call (topic, message, relatedTool, quotedAmount, pages), which materially helps an agent construct a valid payload.

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 names a specific verb and resource — sends one message to the service operators about a price, payment path, or result that did not fit. This is unambiguous and clearly distinct from every sibling tool, which are all comparison/screenshot/report operations.

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 gives explicit when-to-use conditions ('when you stop short of a paid call or a result was not what the task needed') and an explicit exclusion ('Do not call it to report a job failure you can retry'). Both the positive trigger and the anti-pattern are stated, leaving little to inference.

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