notion_read_database

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

The description mentions 'cached rows' hinting at possibly stale data, but does not disclose read-only nature, authentication needs, or any side effects. With no annotations, the description should provide more behavioral context, but it remains minimal.

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?

Single sentence of 13 words that conveys the core action and a key detail (property mapping). No unnecessary words, highly efficient.

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?

Lacks crucial context: which database is read (database selection not addressed), what 'cached' entails, and the return format. With no output schema, the description should explain the output more thoroughly. Incomplete given the tool's simplicity.

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?

Input schema has zero parameters and 100% coverage trivially. The description adds value by explaining that properties are mapped through the schema, clarifying the output structure. Baseline for no parameters is 4, and description meets it.

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 it reads cached rows of a Notion database and maps properties through the schema. This distinguishes it from siblings like notion_list_databases (lists databases) and notion_read_page (reads a single page). However, it does not specify which database is read, assuming a default selection.

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?

No guidance on when to use this tool versus alternatives like notion_list_databases or notion_search. The description does not mention prerequisites or context for using the tool, leaving the agent without decision support.

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