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

No annotations are present, so the description carries the full burden of disclosing behavior. 'Reconcile' does not clarify whether this tool is read-only, performs calculations, or has side effects. It also does not mention what kind of output the agent can expect, whether any state changes occur, or what 'reconcile' concretely produces. This is a major transparency gap for a tool whose name suggests reporting.

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 very short and front-loaded, with no filler. However, it is under-specified rather than concisely complete; six words convey the general subject matter but omit necessary details about the tool's purpose and behavior. It is not bloated, but it does not fully earn its place as a standalone definition.

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?

While the tool has only two parameters and no nested objects, there is no output schema and no annotations, so the description must explain what the tool returns and how it behaves. It does neither. An agent cannot tell whether this is a safe read operation, what shape the reconciliation report takes, or how campaign deliveries and feedback are correlated.

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%: both parameters have basic descriptions ('Campaign ID' and 'Active organization ID'). The tool description adds no additional meaning, so it does not improve on the schema. A baseline of 3 is appropriate because the schema already documents both parameters sufficiently for basic invocation.

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 uses a specific verb ('reconcile') and names the resource ('campaign deliveries and feedback'), so it indicates a reporting/analysis action rather than a generic operation. However, 'reconcile' is ambiguous—it could mean generating a comparison report, adjusting records, or checking consistency—and the description does not clearly distinguish this tool from related siblings like commsharbor_campaign_get, commsharbor_delivery_events, or commsharbor_delivery_get.

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?

No guidance is provided about when to use this tool versus alternatives. With many closely related sibling tools (campaign_get, delivery_get, delivery_events, domain_report), an agent needs some indication of the specific scenario this report addresses, such as matching delivery status against feedback or producing a reconciliation summary. The description implies usage but never states it.

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