notion_personal_read

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

Annotations already declare the safe/idempotent read profile, yet the description adds substantial behavior the annotations cannot convey: repeated calls resume pagination and pending generation, external content is data not instructions, full answers are persisted to answer_path/code_artifacts and not echoed in output.

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?

Purpose is front-loaded and every sentence carries operational information, but the paragraph is dense and mixes usage, parameter routing, security, and output persistence without visual separation, making it harder to scan than necessary.

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 no output schema, the description correctly covers what the return actually is (summarized, with full content saved to local files) plus timeout and side-effect guidance. An agent has everything needed to call and interpret this tool.

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 0%, so the description must carry parameter meaning and does for three of four: job_id and request_key are preferred handles, thread_id resolves latest local task or imports a conversation. It omits any explanation of wait_seconds (default 20, max 300), leaving one parameter's semantics to the schema alone.

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 (read/resume an existing task) and explicitly negates the generating behavior ('without generating'), which cleanly separates it from the ask/submit siblings. An agent can distinguish this from notion_personal_ask without opening either schema.

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?

Explicit routing: prefer job_id or request_key, thread_id resolves the latest local task or imports a conversation. It also gives scope ('Personal chat only; never Custom Agent') and a negative rule for a specific failure mode ('A timeout is not a reason to submit again').

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