notion_get_database

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The word "Get" weakly implies a read-only, non-destructive operation, but there is no statement about permissions, rate limits, or what the returned database object contains (e.g., schema/properties vs. rows).

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 single short phrase is front-loaded and contains no filler or repetition. It is efficient, though its brevity is closer to under-specification than optimal economy for a tool in a crowded sibling set.

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 one-parameter getter with full schema coverage and no output schema, the description is minimally adequate. It still leaves open what is returned (metadata/schema vs. contents) and how it relates to notion_query_database, which matters given the dense sibling ecosystem.

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% (database_id is documented as "Database ID to fetch"), so the baseline is 3. The description's "by ID" merely restates the schema and adds no format, source, or lookup guidance beyond 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?

The description states a clear verb and resource ("Get database by ID"), so an agent knows it retrieves a database object by identifier. However, it does nothing to differentiate this from sibling tools like notion_query_database or notion_get_page, which is the main ambiguity an agent faces in this toolset.

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?

There is no guidance on when to use this tool versus notion_query_database (which returns rows/pages) or notion_search (which finds databases by name). The agent must infer usage entirely from the tool name and sibling names.

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