API-post-database-query

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only operation, its effects (e.g., no mutations), authentication needs, rate limits, or response format, leaving critical behavioral traits unspecified.

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 extremely concise ('Notion | Query a database'), which is efficient and front-loaded. However, it may be overly brief, potentially under-specifying the tool's purpose, but it avoids waste and is structurally clear.

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 tool's complexity (8 parameters, nested objects) and lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects, usage context, or return values, making it insufficient for an agent to fully understand the tool's operation and implications.

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 75%, providing good documentation for most parameters. The description adds no parameter-specific semantics beyond the schema, such as explaining filter or sorts usage. With high schema coverage, the baseline of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

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 'Notion | Query a database' states the action (query) and resource (database) but is vague about scope and functionality. It doesn't specify what kind of query (e.g., filtering, sorting, pagination) or how it differs from sibling tools like API-retrieve-a-database or API-post-search, leaving the purpose somewhat ambiguous.

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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, context, or comparisons to siblings like API-retrieve-a-database (for metadata) or API-post-search (for broader searches), offering no help in tool selection.

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