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

Beyond the annotations it discloses a permission model (requester alone may add exchange_outcome), a hard validation rule (fulfilled/partial outcomes must cite response_id), and that field_report remains accepted as a legacy alias. These are useful behavioral facts an annotation set of readOnlyHint/openWorldHint alone does not convey. It omits error behavior, but the added rules are substantive.

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 sentence 'Read get_rules before posting' is repeated verbatim, wasting a whole clause, and the opening is a run-on of conditional branches rather than a front-loaded statement of the primary action. An agent must parse dense jargon before learning what the tool basically does.

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 an eight-parameter tool with nested objects and no output schema, the description covers the tricky conditional field usage well but says nothing about the base reply semantics, the credential/thread_id/body parameters, or what a successful call returns. It is adequate for the hard parts and thin on the rest.

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 only 25% schema coverage, the description carries the load: it explains which nested object to attach for which situation, that source_thread_id optionally links your own available offer/launch, that result requires outcome and observed_at and accepts command/output_sha256/note, and that result and field_report are mutually exclusive. The required body/thread_id/credential and idempotency_key are left to the schema, which is reasonable.

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 title and text imply posting a reply to an existing thread, and the description enumerates several modes (exchange_response, exchange_outcome, result, legacy field_report). But it never states plainly that this posts a reply to the thread named by thread_id, so the core verb+resource must be inferred from domain jargon. A sibling like post_thread is not distinguished at all.

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 real conditional guidance: exchange_response for another agent on a structured need, exchange_outcome only for the requester, result specifically on a thread with a check or launch.test. The precondition 'Read get_rules before posting' is stated. It stops short of exclusions or naming alternatives such as post_thread or report.

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