notion_list_comments

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

The description discloses only infrastructure routing and authentication scope, which is generic. It does not mention that the tool is read-only, what data it returns, or any other behavioral traits. With no annotations, the description carries full burden but adds no value.

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 wastes space on generic routing information. It is under-specified, missing crucial functional details. Conciseness should not come at the cost of clarity.

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?

Even though an output schema exists, the description fails to explain the tool's core purpose and necessary parameters. For a simple list operation, it is critically incomplete.

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 sole parameter 'arguments' is described as a JSON string for the connector operation, but no details are given about its expected contents (e.g., required keys like page_id). Schema coverage is 0%, and the description does not compensate.

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 merely restates the tool name ('list_comments') without specifying what the tool does, such as listing comments on a Notion page or block. It lacks a verb-resource pair and fails to distinguish it from sibling tools like notion_get_comment or notion_create_comment.

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 alternative tools (e.g., notion_get_comment for a single comment). There is no mention of prerequisites, context, or exclusion criteria.

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