read_section

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

With no annotations, the description fully discloses key behaviors: case-insensitive heading matching, boundary rules, inclusion of heading and recursive children, warnings for unsupported blocks, and special handling of Notion AI meeting-notes. This level of detail is excellent.

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 somewhat lengthy but every sentence serves a purpose. It is front-loaded with the main action and then provides necessary details. Minor trimming could be done, but overall it is well-structured.

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?

Given the lack of output schema and annotations, the description covers all essential aspects: what the tool does, how it works, edge cases (unsupported blocks, meeting-notes), and warnings. It is comprehensive for a read operation.

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?

The input schema already describes both parameters (page_id and heading). The description adds value by noting that heading matching is case-insensitive, which goes beyond the schema. No other parameter details are needed.

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 clearly states 'Read a single page section by heading name,' specifying the verb, resource, and method. It differentiates from sibling tools like read_page and read_block by focusing on sections. The reference to update_section further clarifies its scope.

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?

It provides context on when to use this tool (to read a specific section by heading) and describes boundary rules. However, it does not explicitly state when not to use it versus alternatives like read_block or read_page, leaving some ambiguity.

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