notion_personal_reply

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

With annotations present, the description still adds substantial behavior: the return is a per-turn job_id consumed via read, long answers are persisted to answer_path/code_artifacts rather than returned inline, and external responses are explicitly flagged as data, not instructions. The idempotency guidance around timeouts and request_key reuse reinforces (and does not contradict) idempotentHint=true.

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-loads purpose, then constraints, then return/retrieval behavior; every sentence carries actionable content. It is dense and slightly repetitive around the saved-file behavior, keeping it short of ideal.

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 write tool with no output schema, it covers the return contract, persistence side effects, environment restriction, and retry semantics well. The remaining gap is the undocumented prompt/prompt_file distinction, which matters for correct invocation.

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 50%: request_key has a schema description and prompt_file does too, while prompt and thread_id do not. The description reinforces thread_id ('idle thread') and request_key ('unique key'), but says nothing about prompt vs prompt_file or how to choose between them, so it only partially compensates for the coverage gap.

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 concrete verb+resource ('Send one authorized follow-up in an existing personal conversation') and scopes it ('Personal chat only; never Custom Agent'). It references the read sibling for retrieving results, but never contrasts the tool with notion_personal_ask or notion_personal_submit, so the sibling differentiation is only partial.

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 real preconditions ('Requires an idle thread and a unique request_key') and a recovery rule ('A timeout is not a reason to submit again'), plus routing to read for the correction. It stops short of the explicit when-to-use-this-vs-ask/submit decision the sibling set implies.

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