notion_local_children

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

With no annotations, the description carries the burden and discloses useful behaviors: 'Fast, offline, no API limits.' 'Get' implies read-only. It doesn't mention potential staleness or output format, but goes beyond a minimal description.

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?

Three short sentences, each earning its place: 'PREFERRED for Notion hierarchy' (usage), 'Get all child pages under a page' (purpose), 'Fast, offline, no API limits' (behavior). Zero waste and front-loaded with the most important signal.

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 simple 2-parameter tool, the description covers purpose, usage, and behavioral traits. With no output schema, missing return-format details is a minor gap, but the tool is well-contextualized among its siblings and adequately complete.

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 covers 100% of parameters with clear descriptions (pageId, depth with default). The description's phrase 'all child pages' implies depth-based recursion but adds no syntax details beyond what the schema already provides. Baseline 3 is appropriate.

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?

Description clearly states 'Get all child pages under a page' with a specific verb and resource. The 'PREFERRED for Notion hierarchy' tag hints at its role among siblings but doesn't explicitly name alternatives, so it stops short of a 5.

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?

Explicitly says 'PREFERRED for Notion hierarchy' and gives reasons ('Fast, offline, no API limits') for choosing it. This provides clear when-to-use context, but lacks direct 'when not to use' guidance or named alternatives.

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