notion_query_data_source

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

With no annotations, the description must fully disclose behavioral traits. It only mentions routing details (JWT, tenant, company scope) and does not state whether the operation is read-only, destructive, or what side effects it has. The agent cannot infer safety or permission requirements.

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 but fails to prioritize useful information. It wastes space on routing details that are likely already handled by the platform, while omitting the tool's core purpose. It is not efficiently structured for an agent.

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?

Despite an existing output schema, the description does not explain what the tool returns or how to interpret results. It completely misses behavioral context, parameter details, and usage scenarios, making it inadequate for a connector operation.

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?

The only parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds minimal meaning beyond the schema. Since schema coverage is 0%, the description should provide the structure or allowed keys, but it does not.

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 is a 'Notion connector operation query_data_source' but does not explain what querying a data source accomplishes. It lacks a clear verb+resource description and does not distinguish it from sibling tools like notion_query_database.

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 is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, leaving the agent without decision-making information.

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