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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world write. The description adds genuine behavioral context beyond that: it clarifies the write is only a history line, that Parse still determines completion from the page itself, and that a user confirmation is required. The prompt-injection warning about quotedMaterial is valuable defensive context.

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?

Front-loaded with the trigger condition, followed by effect, caveat, precondition, and safety note. Every sentence carries weight, though the final injection-warning sentence is dense and slightly overpacked.

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 an output schema present and annotations covering the safety profile, the description need not explain return values. It covers trigger, effect, confirmation requirement, and injection risk, which is sufficient for a two-parameter write tool; only sibling disambiguation is missing.

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% for both parameters, including the constraint that id must match what parse_next_tasks returned and the brandSlug default behavior. The description adds nothing about parameters, so the baseline 3 applies.

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 action and outcome: records that the page's editor replied by adding a line to the task's history. It is distinguishable from siblings like parse_mark_sent or parse_dismiss_task, though it never names them. The purpose is clear without being tautological.

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 a clear trigger ('when the page's editor answered the sent message') and an explicit precondition ('Call only after the user confirms'). It does not name a sibling alternative for the near-miss cases (e.g., a non-editor reply), so it falls short of a 5 but still provides real when-to-use guidance.

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