query_view

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

With no annotations provided, the description carries full weight for behavioral disclosure. It transparently describes the temporary nature of the query (creates and deletes) and that it fetches raw page results. However, it does not explicitly state whether the operation is read-only or safe to use, though the lifecycle implies no lasting changes.

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 only two sentences, directly stating the purpose and the key behavioral aspect (temporary query). Every word is necessary, and it is front-loaded with the main action. No extraneous information.

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 moderate complexity, the description covers the main operation and lifecycle. There is no output schema, but 'fetches raw page results' provides some context. It could be improved by hinting at output structure or mentioning pagination parameters explicitly, but it is sufficiently complete for a query 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% (all three parameters documented), so the baseline is 3. The description adds no extra context about the parameters (view_id, page_size, start_cursor) beyond what the schema already provides. Thus, no additional value is added.

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 clearly states 'Query a Notion database view' and details the lifecycle of the operation: creating a temporary query, fetching raw page results, then deleting the query. It uses a specific verb and resource, and given the siblings like 'query_database' and 'get_view', it distinguishes itself as the tool for querying views.

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?

The description implies that this tool is used to query a view's results, but it does not explicitly state when to use it over alternatives (e.g., 'query_database' for databases, 'get_view' for metadata). There is no 'when to use' or 'when not to use' guidance, leaving the agent to infer from context.

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