retrieve-database

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

No annotations given, so description carries full burden. Discloses return type (metadata and data sources), format options, token usage implications, and API version note. Could be more explicit about what 'associated data sources' means, but sufficient for a read operation.

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?

Two sentences plus a note, no redundant information. Every sentence serves a purpose: purpose, return value, usage guidance. Efficiently 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?

Returns vague 'database metadata and associated data sources' without details on fields. No output schema to compensate. With many sibling tools, more specificity would help agents understand what to expect. Adequate but not comprehensive.

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. Description adds value by explaining 'format' parameter usage: 'simple' reduces tokens, 'json' gives full Notion API response. This helps agents choose correctly.

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?

Clearly states verb 'Retrieve' and resource 'database container by its ID'. Describes return type: metadata and associated data sources. Distinguishes from siblings like 'retrieve-page' and 'retrieve-block'. Also notes alternative for schema via 'retrieve-data-source'.

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?

Provides clear context: retrieve database metadata, and for schema use 'retrieve-data-source'. Includes guidance on format parameter for token usage. Lacks explicit when-not-to-use, but the note effectively steers agents away from using this for schema.

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