notion_list_data_source_templates

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

No annotations provided, so the description carries full burden. It mentions routing details but does not disclose behavioral traits like read-only nature, side effects, authentication requirements beyond the JWT/tenant/company scope, or output characteristics.

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 includes unnecessary routing details (e.g., '/api/tools/invoke'). It could be more concise by focusing on the tool's purpose and leaving out implementation specifics.

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?

An output schema exists, so return types are covered, but the description lacks explanation of what data source templates are and how this tool fits into the Notion ecosystem. An agent would not know when or why to use this 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 0%. The description states that 'arguments' is a JSON string of arguments but does not explain what those arguments are or provide any constraints or examples, adding minimal value beyond the schema definition.

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 lists data source templates for Notion, which is a specific verb+resource. However, it does not differentiate from sibling tools like 'notion_list_data_sources' or 'notion_list_databases', leaving ambiguity about what 'data source templates' are.

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 alternatives. The description lacks any context about appropriate use cases or exclusions, making it hard for an agent to decide when to invoke it.

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