notion_query_view

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

No annotations provided. The description only mentions routing details and does not disclose whether the tool is read-only, destructive, requires authentication, or has rate limits. For a tool with no annotations, the description should reveal behavioral traits.

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 short and front-loaded with the purpose. However, it is under-specified, which reduces the value of conciseness. No redundant information, but could be better 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?

Given the complexity (Notion connector with one generic parameter) and the presence of an output schema (not described), the description is incomplete. It fails to explain what querying a view accomplishes or what the response contains.

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 0%, and the description adds minimal value: 'arguments: JSON string of arguments for the connector operation.' It does not explain the structure or allowed fields of the JSON, leaving the agent without guidance on how to construct valid input.

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 it's a 'Notion connector operation query_view', which implies querying a Notion view, but doesn't clarify what a view is or how it differs from similar tools like notion_query_database. The purpose is vaguely clear but lacks specificity and sibling differentiation.

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 guidance on when to use this tool versus other Notion query tools (e.g., notion_query_database, notion_search). Does not mention any prerequisites, constraints, or scenarios.

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