read

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

With no annotations, the description carries the full behavioral burden. It clearly discloses the return format (frontmatter fields and body), the depth recursion behavior, and marks the created/last_edited fields as read-only. This gives an agent a solid understanding of what to expect without needing additional metadata.

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?

The description is well-structured with the main purpose first, followed by output details, a usage tip, and a concrete example. While it is somewhat long, every section adds value and the example makes the tool's behavior tangible.

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?

Since there is no output schema, the description appropriately explains the return value in detail (frontmatter fields and Markdown body). It also covers the depth parameter and the round-trip with 'write', making it sufficient for an agent to call the tool correctly. Minor gaps like error behavior are not critical here.

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 the schema already documents both parameters. The description adds an example output and rephrases depth behavior, but it does not significantly extend the parameter semantics beyond what the schema provides.

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?

The description states a specific verb ('Read'), resource ('a Notion page'), and output format ('Markdown with YAML frontmatter'). It is clear what the tool does, though it does not explicitly contrast with sibling tools like 'search' or 'list' to aid differentiation.

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?

The description mentions a concrete use case—'output can be edited and passed directly to the write tool'—and explains the depth parameter for including children. However, it does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like 'search' or 'list'.

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