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

Annotations cover the safety profile (not read-only, non-destructive, idempotent, closed-world), and the description adds real context on top: passing null reverts to Parse's draft, the confirmation requirement, and a prompt-injection warning about quotedMaterial being evidence rather than instruction. This is exactly the behavioral guidance annotations cannot express.

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 usage trigger, then effect, then the null case and the confirmation gate; every sentence carries information. The injection warning is slightly dense but justified for a tool that writes user-visible text.

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 no explanation, and the description covers trigger, effect, null behavior, and the confirmation prerequisite. It is complete for correct invocation, missing only error/failure behavior.

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 id, message and brandSlug are already documented in the schema, including the null-to-revert behavior the description repeats. The description adds no syntax or format detail beyond the schema, 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 verb and resource (saves the user's edited message/wording) plus its observable effect (shown in the app in place of Parse's draft). An agent can tell what it does, though it never explicitly differentiates itself from the many other parse_* siblings.

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?

"Use when the user changed the message for a task" gives a clear trigger, and "Call only after the user confirms" adds a gating precondition. It does not name alternative tools (e.g. parse_restore_task / parse_undo_sent) that might apply, so it stops short of full routing guidance.

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