query-data-source

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

Mentions pagination and API version, which are useful behavioral details. However, no annotations exist, and the description does not disclose whether the operation is read-only or any side effects, though it is implied by 'Query'. Adequate but not comprehensive.

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?

Three concise sentences, front-loaded with the core purpose in the first sentence, followed by key details on pagination and format. No wasted words.

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 pagination and format choices, but lacks description of return structure (e.g., array of objects). Without output schema, more detail on the response format would improve completeness. Acceptable for a query tool with many parameters.

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?

Adds value beyond the input schema by explaining the default 'simple' format, the restriction of fields to simple format, and pagination cursor usage. With 100% schema coverage, this is above baseline 3.

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 the verb 'Query' and the resource 'Notion data source', with optional filters, sorts, and pagination. Distinguishes from retrieval tool (retrieve-data-source) which likely returns a single source without filtering.

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 usage guidance for format and fields parameters, but does not explicitly state when to use this tool versus alternatives like retrieve-data-source or other query-like tools. Implies usage for filtered queries but lacks when-not-to-use.

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