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

Goes well beyond the annotations: with idempotentHint=false already declared, it explains the practical consequence (retries can duplicate) and prescribes a reconciliation step. It also documents initialization behavior for omitted optionals, the account-access prerequisite, and the negative scope constraints (no author-only restriction, no board transition, no publication, no Scan launch).

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?

Four front-loaded sentences that each carry information: purpose, required inputs, defaulting rules, retry safety, and scope exclusions. Dense but not padded; the only mild redundancy is restating 'Requires title and status' already encoded as required in the schema.

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?

An output schema exists, so return values need not be explained, yet the description still flags the stable activityId, which is the field a caller most needs. Combined with non-idempotency, defaulting, and scope boundaries, it covers what an agent needs; only permission granularity ('Account access applies' is vague) is left thin.

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 coverage is 71% and the schema's own notes are phrased for update semantics ('omission preserves on update'). The description usefully re-anchors create semantics by stating that omitted description/date/references initialize to null/null/empty, and restates the required title/status. It adds real meaning over the schema, though it does not explain the status enum's operational meaning.

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+resource ('Create one action') and names the returned artifacts (saved action, stable activityId). It also carves out scope relative to siblings by declaring 'No external publication or Scan launch', which rules out record_recommendation_publication and trigger_scan, though it never names the closest sibling (create_recommendation / update_recommendation_action) directly.

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?

Gives concrete when-to-use guidance: after an uncertain outcome, read list_recommendation_actions before retrying, because repeating creation can duplicate. It also states the precondition ('Account access applies') and required fields. It stops short of explicitly routing to alternatives for adjacent needs (e.g. update vs create), so it is clear context without full exclusion guidance.

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