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

No annotations exist, so the description carries the full burden. It does add real context beyond the schema — 'append' implies additive, non-destructive writes, and 'Free — costs 0 credits' is a cost signal unavailable anywhere else. However, it omits permission/auth needs, duplicate or re-log behavior for the same person and action, and what happens when the person_id or campaign_id does not exist.

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 sentences, front-loaded with the action and followed by the usage rationale. Nothing is padding; even the cost clause is a distinct fact.

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 4-parameter write with full schema coverage and no output schema, the description covers purpose, trigger events, downstream effect, and cost. The remaining gap is duplicate/error behavior, which matters for a logging tool but is a single omission rather than a systemic one.

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 all four parameters are already documented in the schema, giving a baseline of 3. The description restates the action values in plain prose but adds no new semantic detail such as idempotency per action or how note is stored or surfaced.

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 and resource ('Append an entry to the outreach log') scoped to a Constellation campaign. It also names the downstream consumer, get_campaign_stats, which makes the tool's role in the sibling set unambiguous.

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?

Explicitly says when to use it by enumerating the four recordable events (connection requests, acceptances, replies, no-responses) and the purpose (feeding rate stats). No when-not guidance or exclusion versus a hypothetical update/delete counterpart, which keeps it out of the 5 tier.

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