notion_get_comment

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

No annotations provided, so description carries full burden. It mentions routing infrastructure but does not disclose whether the tool is read-only, requires permissions, or has side effects. Lacks detail on 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?

Description is short but wastes first sentence restating the name. Second sentence adds routing detail irrelevant to agent usage. Not concise in a value-adding sense.

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?

With an output schema present but undocumented, no mention of return values, and no differentiation from many sibling tools, the description is severely incomplete for agent decision-making.

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?

Single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation' – a tautology. Schema coverage is 0%, yet description provides no meaningful constraints or examples (e.g., expected keys like comment_id).

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?

Description merely restates the tool name as 'Notion connector operation get_comment', without specifying what it retrieves (e.g., a comment by ID? All comments?). It fails to differentiate from siblings like notion_list_comments 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 on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions despite many sibling notion tools with overlapping functionality.

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