Query Data Source

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context on pagination and formats but does not disclose additional behavioral traits like rate limits or auth needs. Moderate added value.

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-sentence description is front-loaded with purpose and sibling guidance. No wasted words; every sentence earns its place.

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?

Covers core functionality, sibling alternative, and parameter usage well. Lacks explicit mention of return value structure (no output schema), but annotations hint at read-only retrieval. Slightly incomplete for a complex tool.

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 coverage is 100%, baseline 3. The description enhances parameters with usage hints, e.g., when to use 'json' vs 'markdown' and 'compact' vs 'full', adding meaning beyond the schema.

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 'Query a Notion data source with filters, sorts, and pagination,' clearly specifying verb, resource, and capabilities. It also distinguishes from sibling tool notion_retrieve_database by advising when to use that first.

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 tells when to use notion_retrieve_database as an alternative. Additionally, parameter descriptions for 'format' and 'response_mode' provide usage guidance. Lacks explicit 'when not to use' but still clear context.

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